Skip to main content
Glama

List website pages

list_site_pages
Read-onlyIdempotent

List public motifyme.co pages (guides, tools, finance pages, fuel price pages) from the sitemap, optionally filtered by keyword.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_site_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNokeyword in the url

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description does add genuine context beyond that by naming the source ("from the sitemap") and the scope ("public" pages only), which explains why the tool is closed-world. However, it says nothing about result volume, ordering, or whether large sitemaps are truncated, which matters for a listing 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?

A single well-formed sentence with no filler; the scope statement comes first, followed by the filter, so the agent reads the most important constraint up front. Nothing in it is redundant with the schema or 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?

For a one-optional-parameter read-only listing tool with no output schema, the definition covers source, scope, and filtering adequately; return-value explanation is correctly omitted. The only real gap is what a result entry looks like (URLs versus titles) and whether results are capped, which an agent would want before calling on a large sitemap.

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 a single optional parameter already documented as "keyword in the url", so the baseline is 3. The description's phrasing "filtered by keyword" is slightly looser than the schema's "keyword in the url" and adds no matching semantics (substring vs. exact, case sensitivity) beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("List public motifyme.co pages") and enumerates the page categories covered (guides, tools, finance pages, fuel price pages), which tells an agent exactly what corpus it draws from. It does not explicitly distinguish itself from the sibling get_site_page, but the listing-versus-fetching distinction is strongly implied by "List" plus the enumerated categories.

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?

"optionally filtered by keyword" implies the intended usage pattern (browse all, or narrow with a query), but there is no explicit when-to-use versus when-not, and no pointer telling the agent to use get_site_page once it has identified a specific page. The guidance is implied rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources