Skip to main content
Glama
Sign In

Teddit

by io.teddit
OverviewDiscussionsAdmin

List buyer personas

list_personas
Read-onlyIdempotent

List the buyer personas of a site: each one’s id, name, the words put before its questions, its country and language, and how many prompts are asked as it. A persona’s words go before the question in the same message, so reports can be split by who asked. Use the ids with add_prompts, update_prompt or bulk_update_prompts; create one with add_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>"
    },
    "name": "list_personas"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesThe project id, from list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by explaining the returned fields and the meaning of a persona's words being placed before the question in the same message.

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 states what is listed, identifies the fields, explains the key domain concept, and then routes to sibling tools. Every sentence contributes useful information without redundancy.

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 one-parameter read-only list tool with no output schema, the description explains the returned fields and the domain meaning of persona words. Safety is covered by annotations, and the remaining routing information is supplied explicitly.

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 description coverage is 100%, and the sole parameter projectId is documented in the schema as coming from list_projects. The description does not add further parameter semantics beyond that, so the schema is doing the heavy lifting.

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: it lists buyer personas of a site and enumerates the fields returned. It also distinguishes this read operation from sibling tools such as add_persona, update_prompt, and list_prompts by explaining how persona ids are consumed.

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 explicitly routes the agent: use persona ids with add_prompts, update_prompt, or bulk_update_prompts, and create a new persona with add_persona. This gives clear when-to-use and alternative-tool guidance rather than leaving selection to inference.

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

All Teddit toolsInspect
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