Teddit

Trends of a site

get_trends

Read-onlyIdempotent

Get one site’s history week by week: the overall numbers and each week’s change, how many prompts started and stopped naming the brand each week, each topic’s share per week, and the prompts grouped as held (named every week), volatile, or lost (named before, not for 2+ weeks: the repair list). Use it to see the direction over time; get_dashboard covers a single week.

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": "get_trends"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Max prompts per stability list. Default 25.
`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, idempotentHint, and destructiveHint=false, so the agent knows the safety profile. The description adds substantial behavioral detail by explaining exactly what data is computed and returned (weekly changes, topic shares, prompt stability categories), including the definition of 'lost' (not named for 2+ weeks). It does not cover pagination or truncation behavior, but that is a minor gap given the annotations.

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

Conciseness4/5

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

The description is front-loaded with purpose and key outputs, then closes with usage guidance. It is somewhat dense in a single sentence with colons and semicolons, but every clause earns its place by clarifying what the tool returns or when to use it.

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?

For a tool with no output schema, the description thoroughly explains the returned data and its semantics, including the stability categories. It does not mention the time range or pagination behavior, which would help for a history tool, but the core information an agent needs to call it correctly is present.

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%, with both parameters already documented in the input schema. The description indirectly connects to the 'limit' parameter by mentioning prompts grouped as held/volatile/lost, but it adds no new syntax, format, or constraints beyond what the schema provides.

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 ('Get') and resource ('one site’s history week by week'), then enumerates the exact data returned: overall numbers, weekly changes, prompt naming starts/stops, topic shares, and stability groups (held/volatile/lost). It explicitly distinguishes itself from the sibling get_dashboard by noting that get_dashboard covers a single week.

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?

Directly says 'Use it to see the direction over time' and names the alternative 'get_dashboard covers a single week', giving an explicit condition for choosing this tool over its sibling.

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?