/**
 * CMS Posts tools — consolidated STRAP surface:
 *   list_cms_posts        — search/filter (distinct list schema)
 *   cms_post              — read-only: action ∈ {get, get_by_slug, performance}
 *   write_cms_post        — action ∈ {create, update} (shared body once; agent_authored)
 *   bulk_cms_posts        — action ∈ {publish, unpublish, delete} over 1–25 ids
 *   import_cms_posts      — async bulk import
 *   get_cms_import_status — poll an import job
 *
 * The whole surface ships in one stdio `tools/list` message under the 64KB
 * Windows pipe limit; consolidating the CRUD/lifecycle verbs behind an `action`
 * param keeps every capability advertised upfront + immediately callable while
 * shrinking the advertised byte count (the STRAP pattern).
 */
import type { McpToolDefinition, ToolContext, ToolResult } from "../types.js";
import { type ContentType } from "../content-types.js";
export declare const CONTENT_TYPE_LABELS: Record<ContentType, string>;
/**
 * Render a CMS post's body under the same verbatim contract as get_content:
 * the assistant summarizes long tool output unless told
 * otherwise, and the old 2,000-char cap was a genuine data-loss path for
 * full posts. Cap at 50K chars like get_content.
 */
export declare function renderCmsPostBody(content: string | null | undefined): string;
export declare const cmsPostTools: McpToolDefinition[];
export declare const cmsPostExecutors: Record<string, (input: unknown, context: ToolContext) => Promise<ToolResult>>;
//# sourceMappingURL=cms-posts.d.ts.map