Teddit

Update a prompt

update_prompt

Destructive

Edit one tracked question: its text, category, intent, funnel stage, status (active, paused, draft) or persona. Fields left out keep their value. Stored answers keep their history; the change applies to future scans. Returns the updated prompt. For many prompts at once use bulk_update_prompts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>",
      "promptId": "<promptId>"
    },
    "name": "update_prompt"
  }
}

Input Schema

Name	Required	Description
`text`	No	The new question text.
`funnel`	No	Funnel stage of the question.
`intent`	No	What the buyer wants.
`status`	No	active, paused or draft.
`category`	No	A new category.
`promptId`	Yes	The prompt id, from list_prompts.
`personaId`	No	Ask as this buyer persona; null asks it bare.
`projectId`	Yes	The project id, from list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the destructiveHint=true and readOnlyHint=false annotations, the description explains that omitted fields retain values and that stored answers keep their history while changes apply to future scans. It also states that the updated prompt is returned, giving useful post-call expectations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: it opens with the operation, lists updatable fields, then explains persistence and the bulk alternative. Every sentence contributes useful selection or behavioral context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive single-record update with rich schema coverage and annotations, the description provides the missing operational context: partial update behavior, history preservation, future-scan effect, return value, and the bulk alternative. No output schema is needed because it states that the updated prompt is returned.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds meaningful partial-update semantics not captured by the schema: unspecified fields are preserved. It also clarifies that persona corresponds to asking as a buyer persona, though the schema already documents most parameter details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: edit one tracked question. It enumerates the editable fields and explicitly distinguishes the single-prompt operation from bulk_update_prompts, so an agent can identify it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly frames this as a single-prompt edit and routes multi-prompt changes to bulk_update_prompts. The partial-update behavior is also stated directly: fields left out keep their value.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Teddit tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?