FoxCue MCP Tools Reference: Hosted Directory Profile

Hosted FoxCue MCP tools for knowledge, ideas and scripts, plus the brand-setup, transcript and keyword work the directory profile can do.

The hosted FoxCue MCP endpoint uses the directory profile (remote_profile is directory on GET /api/v1/capabilities). Connect your assistant with OAuth first. The tool list in your client is the current input schema. Approved scopes and workspace ownership still control each call.

There are two hosted profiles, workflow (55 tools) and directory (35 tools). Which one is live depends on your workspace configuration. A live capabilities check on 2026-10-28 reported remote_profile directory. Your workspace may differ.

  • Directory tools: all 35, with inputs and outputs.
  • Workflow-only tools: the 20 tools directory does not include (publishing, citation checks, video claims, library).
  • Brand setup is the 16 brand tools, also listed in the directory page.

The names, scopes and schemas on those pages come from the tool registrations. result is typed as unknown for most tools, so the return value is the API payload and is not given invented fields.

Hosted tools

ToolWhat it does
workspace_capabilitiesRead the profile's implemented capabilities and limits; its scopes are supported permissions, not the connection's approved grant
search_workspaceSearch a selected family of owned brands, silos, sources or scripts by title
inspect_recordRead an owned brand, silo, source, script or planned video by its returned ID
add_sourceSave source text or import one public website URL. New sources default to internal visibility
search_sourcesRetrieve permitted source passages with lexical search; no model or embedding calls
suggest_video_ideasUse one public article URL or saved public website source to queue bounded idea planning for a brand and silo
list_video_ideasRead saved silo ideas, their evidence, gaps and accepted-video links
accept_video_ideaAccept a current evidence-ready idea into the canonical video plan
write_video_scriptPrepare a planned video's brief and draft, or explicitly queue paid text writing
generate_scriptQueue standard or long-form writing for an existing script and its current revision
revise_scriptSave supplied script edits using the latest expected_updated_at; status labels such as published are editorial metadata and do not upload content
inspect_runRead an existing source-to-ideas workflow, idea run or script-generation job
cancel_runRequest cancellation of supported idea or script-generation work; completed work remains saved

Adding a source changes the workspace. Supplied text does not call a model; fetching a URL can incur extraction-provider charges. Idea planning and script generation can also incur configured provider charges. Source import is not request-idempotent: check for the saved source before repeating an import after an uncertain response.

Article to script

  1. Find the intended brand and silo. Use one readable public article URL or an existing public website source from that brand; a note or YouTube URL is not a substitute for this planning input.
  2. Call suggest_video_ideas with the brand, silo, one URL or source ID, a bounded count and a stable idempotency key.
  3. Keep the returned workflow and child-run IDs. Use inspect_run, then list_video_ideas to show actual saved ideas and any evidence gaps.
  4. Use accept_video_idea for the supported idea you choose, with its current revision and stable request key.
  5. Use write_video_script with the returned video ID. generate=false prepares a draft; generate=true explicitly queues paid writing. Poll the returned job rather than creating replacement work.
  6. Read the saved script before editing. Pass its actual updated_at as expected_updated_at to revise_script. A revision conflict requires a fresh read and reconciliation.

Missing sources, unavailable providers or a generation cost limit can block writing. An assistant should report these issues rather than invent finished ideas or narration. Legacy Strategy budget settings do not enforce a spending limit; approve the work and its allowance explicitly. Evidence-readiness and coverage hints help review; they do not prove every claim is supported.

Hosted limits

Logo import through brand setup is a raster image up to 2 MiB (the brand-kit image route). A keyword run's budget_usd defaults to $1 for discover or refresh and $0.50 for enrich, and it cannot exceed $10. The run stops before it passes that budget.

Ask the assistant to work within the tool list it was given. Publishing, recording edits and renders belong to the local workflow profile or the app, not to a grant that only has the directory scopes. Citation checks are a strategy API (POST /strategy/growth/checks) and need the scopes that route requires. They are not a silent extra on an old grant.

Long operations return durable IDs. Reuse the same idempotency key and inputs after an uncertain acknowledgement for operations that support them. Cancellation and revocation cannot undo provider calls already sent or their charges.

Local workflow and legacy profiles

Local stdio installations can select broader profiles. These additional workflow tools are not part of the hosted 13-tool connector:

ToolAdditional local workflow
discover_targetsPropose buyer questions from source evidence
review_targetsReview and approve proposed targets
inspect_productionRead a saved composition
edit_videoStart editing an owned recording
render_videoRender a selected composition revision
read_measurement_reportRead retained supported measurement evidence

This table is not the complete broader profile catalogue. Existing integrations should inspect their own tool list and scopes. Changing the local profile does not expand a hosted OAuth connection's tool set.

On this page