Tools

Overlap MCP tools are grouped by user goal. The client supplies typed inputs, while the server verifies the signed-in user’s live membership in the requested organization and enforces roles, revisions, and confirmation requirements. Tool IDs use underscores so they remain compatible with Claude and other clients that accept only letters, numbers, underscores, and hyphens in tool names.

​

Context and discovery

• overlap_organizations_list — list all current Overlap memberships and their organization IDs
• overlap_context_get — target organization, current role, and available capabilities
• overlap_search — paginated search across supported Overlap entities
• overlap_docs_search — search the current Overlap documentation catalog

Organization listing makes one user-scoped Clerk membership request and does not fan out into one API request per organization. It returns an organizationId, display name, current role, and available tools. Pass that value as organization_id to any organization-scoped tool. If omitted, the tool uses the organization selected during OAuth as the default. Organization IDs are selectors, not credentials; Overlap rechecks membership and validates the company when an organization is actually used.

​

Workflows and runs

• overlap_workflows_list
• overlap_workflows_get
• overlap_workflows_preflight — freezes the workflow revision and reports external effects
• overlap_workflows_run
• overlap_runs_get
• overlap_runs_cancel

At the start of a fresh conversation, the assistant lists your current organizations before its first organization-scoped action unless you have already named and resolved an exact organization. If multiple organizations are available and the target is uncertain, it asks you to choose before continuing. Before preflight or execution, the assistant resolves the request to exactly one workflow. If no workflow or multiple plausible workflows match what you asked for, it lists the candidates and asks you to choose instead of guessing. It also asks for a required source URL or other runtime input when that information is missing, and obtains explicit written consent before starting the run. Workflow execution is available anywhere the connected user has a current organization membership; it does not require MCP to be activated separately for each organization. Every MCP run still uses a one-use start proof bound to the exact organization, workflow revision, and input. A supported workflow with external effects requires confirmation before it runs. Social workflow nodes can create reviewable drafts but cannot authorize publishing. Email, partner-export, and unknown external-effect nodes remain unavailable through MCP until they have equivalent durable dispatch protection.

​

Clips, transcripts, and renders

• overlap_clips_search
• overlap_clips_get
• overlap_clips_update
• overlap_transcripts_get
• overlap_transcripts_replace
• overlap_clips_render
• overlap_operations_get

overlap_clips_search uses the Clips page’s library search model. It supports text search plus tag, status-tag, people (any or all), keyword, workflow, aspect-ratio, duration, and modified-date filters. Set include_facets to return available tag, status, people, keyword, workflow, and aspect-ratio counts. Search results are compact summaries and omit editing configuration such as subtitleConfig, titleConfig, and watermark settings; use overlap_clips_get when those details are needed. To enumerate one episode, pass the exact live_... value from its portal URL as episode_id, request up to 100 clips, and continue with meta.cursor until it is absent. Episode and workflow-run filters read the matching clip lineage directly from the organization’s Clips collection, so they are not limited to the first page of the general library index. General text and facet searches use the same Algolia indices and replica sorts as the Clips page. When only the number of matching clips is needed, set count_only: true. The response contains no clip objects and returns the count in meta.total, which avoids loading an episode’s full result set into the conversation. Clip and transcript writes use an expected version. If someone edits the clip after it was read, the server returns a conflict instead of overwriting the newer version. Renders are synchronous: the tool waits for rendering to finish and returns the completed renderUrl.

​

Social Calendar

• overlap_social_accounts_list
• overlap_social_calendar_list
• overlap_social_posts_get
• overlap_social_posts_create_draft
• overlap_social_posts_update
• overlap_social_posts_authorize — confirm and publish an immediate draft
• overlap_social_posts_cancel

Draft creation never authorizes publication. Future times may be used for calendar planning, but future scheduled publishing is unavailable during the beta. Set scheduledAt to null before requesting immediate-publish confirmation. The assistant shows the immutable preview and asks for explicit written consent in chat; it never opens a browser for action confirmation. Once a post is scheduled or publishing, cancel its existing work before making a material edit; Overlap will not replace authorized copy in place. Calendar queries are limited to a 93-day range. Times are returned as RFC3339 values and natural-language scheduling uses the organization timezone.

​

Analytics

• overlap_analytics_summary
• overlap_analytics_posts_list
• overlap_analytics_posts_get
• overlap_analytics_trending

Analytics tools use cached Overlap data and report freshness and platform coverage. They do not trigger live provider refreshes.

​

Pagination and retries

List tools return opaque cursors and at most 100 records per page. Mutations use idempotency receipts so a network retry returns the original response instead of repeating a workflow, render, or publish action.