Teddit

Update or delete many prompts

bulk_update_prompts

Destructive

Change many prompts at once (up to 5000 ids): set their status, intent or persona, re-file them under one category (category), add one to the categories they have (addCategory) or take one off (removeCategory), or delete them (delete=true, cannot be undone). Typical uses: activate reviewed drafts, pause a batch that is done measuring. Returns how many changed. For one prompt use update_prompt.

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>",
      "ids": "<ids>"
    },
    "name": "bulk_update_prompts"
  }
}

Input Schema

Name	Required	Description
`ids`	Yes	Prompt ids, from list_prompts.
`delete`	No	true deletes the prompts instead of changing them. Cannot be undone.
`intent`	No	Set every prompt to this intent.
`status`	No	Set every prompt to this status.
`category`	No	File every prompt under this one category, replacing the ones they have.
`personaId`	No	Ask the prompts as this buyer persona; null asks them bare.
`projectId`	Yes	The project id, from list_projects.
`addCategory`	No	Add this category to the ones they have.
`removeCategory`	No	Take this category off.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description still adds real value with the 5000-id cap, the irreversibility of delete, and the return value ('how many changed'). What it doesn't disclose is whether multiple mutation fields can be combined in one call or how partial failures are reported — meaningful gaps for a bulk mutation tool.

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 operation list is front-loaded in one dense sentence, followed by a short usage sentence and a routing sentence. Every clause carries new information — no filler, no restating of the title.

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

Completeness4/5

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

Covers the destructive path, the batch limit, and the return shape, which is what an agent needs for a 9-parameter bulk mutation with no output schema. It stops short of explaining field combinability and partial-failure behavior, which matter at this complexity level.

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

Parameters3/5

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

Schema coverage is 100% and the per-parameter descriptions already spell out replace-vs-add semantics for category, addCategory and removeCategory. The description reinforces that mental model but adds no syntax, format, or exclusivity rules beyond the schema, so the baseline of 3 applies.

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?

States a specific verb (change/update/delete), the resource (many prompts), the batch bound (up to 5000 ids), and enumerates the exact operations available. It explicitly distinguishes itself from update_prompt for the single-prompt case, so an agent can route correctly without opening either 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?

Gives concrete when-to-use scenarios ('activate reviewed drafts, pause a batch that is done measuring') and names the alternative tool update_prompt with the condition that selects it. It also flags the delete path as irreversible, which steers the agent away from accidental destruction.

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?