Skip to main content
Glama
Sign In

Teddit

by io.teddit
OverviewDiscussionsAdmin

Cited pages of a site

list_pages
Read-onlyIdempotent

List the pages of a site (from its sitemap) with, for each, which assistants link to it in their current answers and for how many prompts. shown=no finds the pages the assistants never show, shown=yes the ones they do; q searches title and URL. Paginated. If the list is empty, run import_sitemap first.

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_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoText to search for in the title or URL.
pageNoPage number, from 1.
shownNoyes = pages some assistant links to; no = pages none does.
perPageNoPages per page, 5–200.
projectIdYesThe project id, from list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so the description only needs to add operating context — and it does: results are paginated, and an empty list signals a missing sitemap rather than zero data. Return-payload shape is sketched, though per-page limits and ordering are not disclosed.

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 purpose is front-loaded in the first clause and every sentence carries information about filtering or fallback behavior. The dense run-on construction with semicolons makes it slightly harder to parse but wastes no words.

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

Completeness3/5

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

With no output schema, the description does carry the burden of explaining return values, and it names the cited-assistants and prompt-count fields. However, for a five-parameter paginated listing tool it omits pagination metadata and ordering, leaving the agent partially blind about the response envelope.

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%, so every parameter is already documented. The description's notes on 'shown' and 'q' largely restate the schema wording ('yes = pages some assistant links to'), adding only marginal clarity, which lands at the baseline for a fully documented schema.

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 and resource ('List the pages of a site (from its sitemap)') and goes on to define the distinctive payload: which assistants link to each page and for how many prompts. That payload detail separates it from generic list tools such as list_prompts or list_projects without the agent needing to open 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 Guidelines4/5

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

Gives concrete selection conditions for the 'shown' filter and for 'q', and routes the agent to a sibling when the result is empty ('If the list is empty, run import_sitemap first'). It never states when to use this tool instead of other listing tools, so it stops short of full alternative routing.

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