Skip to main content
Profound MCP gives AI assistants tools to see which prompts a category tracks, read the answers AI engines gave to them, create new prompts, update existing ones, and activate, disable, or delete them in bulk. To connect your MCP client to the hosted server, refer to the Connection guides.

How the tools work together

1

Resolve the category

Prompts are scoped to a category, so before doing anything with prompts, the assistant resolves the category with list_categories.
2

See what you track

Ask which prompts the category runs. The assistant lists them with list_prompts, narrowing by status, topic, or tag when you ask for it.
3

Read the answers

Ask what AI engines say. The assistant retrieves the raw answers behind the metrics with get_prompt_answers.
4

Create or revise

Ask to track new prompts and the assistant drafts and previews them with create_prompts. Ask for a change to existing prompts and it previews field-by-field changes with update_prompts.
5

Activate, disable, or delete

Ask to pause prompts, resume them, or remove them for good. The assistant transitions them in bulk with update_prompts_status.

Behavior and safety

Write tools default to preview mode: the assistant receives a plan of the change first, and nothing persists until it applies that plan with preview: false.

Behaviors

MCP hints

The read tools (list_prompts and get_prompt_answers) only retrieve data and change nothing in Profound. The following MCP hints are set on the write tools:

Prompt tools

Lists the prompts configured in a category, with their IDs and details. The other prompt tools take prompt IDs from this list.Example prompts:
  • “Which prompts are we tracking in the Banking category?”
  • “Show me the disabled prompts under the savings accounts topic.”
Inputs
Retrieves the answers AI engines gave for a category’s prompts over a date range: the raw text behind the visibility metrics.Example prompts:
  • “What did AI engines answer for our savings prompts last week?”
  • “Pull the answers behind last month’s visibility drop.”
Inputs
Creates one or more prompts in a category. Each prompt names the question to ask, the topic it belongs to, and the platforms and regions to run it on.Example prompts:
  • “Start tracking ‘What are the best running shoes for flat feet?’ on ChatGPT in the US.”
  • “Create prompts for these questions under the savings accounts topic.”
InputsEach entry in prompts accepts:Notes:
  • Topic and tag names are matched exactly: a misspelled name creates a new topic or tag instead of joining the existing one, splitting your data between the two. The preview counts these in topics_created and tags_created, so check it for unintended new topics or tags before confirming.
  • Creates aren’t idempotent: applying the same call twice creates duplicate prompts.
Updates one or more existing prompts. The preview returns a field-by-field comparison per prompt: old and new values for single fields, and added and removed values for collections.Example prompts:
  • “Move the pricing prompts to the ‘Fees’ topic.”
  • “Tag the savings prompts with ‘high priority’.”
InputsEach entry in prompts accepts:Notes:
  • For tags, regions, platforms, and personas fields, passing null doesn’t change the value, [] clears it, and a non-empty list replaces the whole set. To add one tag, the assistant submits the complete tag set including the existing tags.
Changes the status of prompts:
  • active - resumes daily runs
  • disabled - stops future runs and preserves history
  • deleted - permanently deletes the prompts and their historical data
Use the deleted status with caution: it permanently removes the prompts and their historical data.
Example prompts:
  • “Disable the holiday prompts, we’ll bring them back in November.”
  • “Delete the test prompts you created earlier.”
InputsNotes:
  • Applying the status to prompts that already have this same status doesn’t change anything.