Skip to main content
Glama
Sign In

pageaudit

by online.pageaudit
OverviewDiscussionsAdmin

List site fix prompts

list_site_fix_prompts
Read-onlyIdempotent

Find saved sites prompts before generation. Listing is free. Keep language and source filters when following the cursor. At most 100 saved rows per page, plus up to three earlier free audit receipts. Follow _links.next. A legacy receipt has id=null and legacy=true; the matching generation recovers it without a debit. The result belongs to the authenticated owner and active organization.

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": {
      "id": "<id>",
      "source": "<source>"
    },
    "name": "list_site_fix_prompts"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOwned source ID.
afterNoCursor from the preceding page.
sourceYesweekly: a saved weekly report. search_console: saved Search Console opportunities.
languageNoPrompt language: en (default) for English or pt for Portuguese.
report_idNoRequired for weekly.
guest_tokenNoPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / guest_token / description
      Added value: +"Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources."
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description still earns credit by disclosing cost ('listing is free'), page composition (up to 100 saved rows plus up to three free audit receipts), pagination mechanics ('Follow _links.next'), legacy receipt behavior (id=null, legacy=true, no debit on regeneration), and ownership scoping to the authenticated owner and active organization.

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?

Purpose and cost are front-loaded in the first two short sentences, then pagination then legacy semantics, so the agent gets orientation before detail. The phrasing is terse and mildly jargon-heavy ('free audit receipts'), but no sentence is filler.

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?

With no output schema, the description carries the return-shape burden and does so: row counts, appended audit receipts, _links.next, and legacy rows are all described. What remains thin is how the required id/report_id pair interacts with 'source' across the weekly vs search_console branches, which the agent must piece together from the schema.

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 real meaning the schema does not: that language and source filters must be preserved when following the cursor, which governs correct use of 'after'. It also clarifies the id=null legacy case that would otherwise confuse the required 'id' field.

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 names a specific verb+resource combination (finding/listing saved site prompts) backed by the title 'List site fix prompts', so an agent knows this is a retrieval tool. It stops short of distinguishing itself from close siblings such as list_audit_fix_prompts and list_domain_fix_prompts, which share nearly identical framing.

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?

'Find saved sites prompts before generation' and 'the matching generation recovers it without a debit' imply the intended workflow — call this before generate_site_fix_prompt. There is no explicit statement of when NOT to use it or which sibling to choose for audit- or domain-scoped prompt listings, so routing to the correct list_* tool remains an inference.

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

All pageaudit 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