/**
 * Next-actions tool
 *
 * One call that answers "what should I do now on this site": the ranked,
 * cross-domain list the Home page shows, read as stored from
 * GET /next-actions. Nothing is ranked here; the tool renders the route's
 * deterministic CTAs and resource pointers and names the tool to call next,
 * so an agent never has to reconcile list_opportunities with the AI-visibility
 * tools itself. list_opportunities keeps its own contract untouched (R4).
 */
import type { McpToolDefinition, ToolContext, ToolResult } from "../types.js";
interface NextActionResource {
    type: "opportunity" | "content" | "audit" | "audit_run" | "ai_visibility_prompt";
    id: string;
}
/** Public domain vocabulary of the route, as a person reads it. Pinned to the wire owner app-side. */
export declare const DOMAIN_LABELS: Record<string, string>;
/**
 * The tool to call next for each resource the route can point at, and the
 * input the resource id fills. Pinned to the wire owner app-side.
 */
export declare const NEXT_TOOL_BY_RESOURCE: Record<NextActionResource["type"], {
    tool: string;
    arg: string;
    needs?: string;
}>;
/**
 * The tool that covers an item's area when the action lands on a page rather
 * than a row (an analytics insight): a tool-only agent has no browser, so the
 * pointer must be a tool. `siteScoped` says whether the tool takes site_id;
 * one that does not is named bare, never with an input it would drop.
 * Pinned app-side against the tools' own schemas.
 */
export declare const NEXT_TOOL_BY_DOMAIN: Record<string, {
    tool: string;
    siteScoped: boolean;
}>;
export declare const nextActionsTools: McpToolDefinition[];
export declare const nextActionsExecutors: Record<string, (input: unknown, context: ToolContext) => Promise<ToolResult>>;
export {};
//# sourceMappingURL=next-actions.d.ts.map