Teddit

Update a buyer persona

update_persona

Destructive

Change a buyer persona’s name, words, country or language. Fields left out keep their value; null for country or language returns to the site’s. Future scans ask with the new words; every stored answer keeps the words it was asked with. Returns the updated persona.

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>",
      "personaId": "<personaId>"
    },
    "name": "update_persona"
  }
}

Input Schema

Name	Required	Description
`name`	No	A new short label.
`context`	No	New words to put before each question.
`language`	No	The language this buyer asks in; null returns to the site’s.
`location`	No	The country this buyer is in; null returns to the site’s.
`personaId`	Yes	The persona id, from list_personas.
`projectId`	Yes	The project id, from list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is partly covered. The description adds genuinely new behavior: omitted fields are preserved, null on country/language reverts to the site default, and the change is forward-only for scans while already-stored answers retain their original wording. It stops short of stating permission requirements or whether a revert can be undone.

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?

Four short sentences, each carrying distinct information, with the core action front-loaded and the side-effect caveat (stored answers keep old words) placed before the return note. No filler or restatement of the title.

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 6-parameter mutation tool with no output schema, the description covers action, partial-update semantics, null-reset behavior, downstream effect on scans, and return value ('Returns the updated persona'). Nothing material is missing for an agent to call it correctly.

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 coverage is 100%, so the baseline is 3, but the description adds semantics the schema does not: partial-update/leave-out behavior and the distinction between omitting a field and explicitly passing null. It also glosses 'words' as the context field, bridging the description's vocabulary to the schema's parameter name.

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?

Names a specific verb (Change) and resource (a buyer persona) plus the exact editable facets (name, words, country, language). An agent can distinguish it from add_persona, remove_persona and update_project without opening any schema.

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

Usage Guidelines3/5

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

It gives strong how-to-call guidance ('Fields left out keep their value') which tells the agent this is a partial update, not a replace. However, it never names alternatives or states when not to use it (e.g. to rename a project use update_project, to add a persona use add_persona), so routing must be inferred from the tool name alone.

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?