Skip to main content
Glama
Sign In

pageaudit

by online.pageaudit
OverviewDiscussionsAdmin

List audit fix prompts

list_audit_fix_prompts
Read-onlyIdempotent

Find saved audits 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>"
    },
    "name": "list_audit_fix_prompts"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOwned source ID.
afterNoCursor from the preceding page.
languageNoPrompt language: en (default) for English or pt for Portuguese.
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

A4.2/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses that listing is free, the page size cap of 100 rows, the extra allowance of up to three earlier free audit receipts, the cursor mechanism via _links.next, and the legacy receipt shape (id=null, legacy=true) that is recovered without a debit. It also states the ownership scoping to the authenticated owner and active organization — substantial behavior an agent could not know from annotations alone.

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 short, front-loaded with purpose and cost, then moves to pagination rules and edge cases in a logical order. Sentences are terse to the point of being clipped ('Find saved audits prompts before generation'), and the '_links.next' reference assumes output structure not documented anywhere else.

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 burden of explaining return shape and does so reasonably: page size, extra receipts, cursor link, and legacy rows. It is not fully complete on what a 'saved row' contains or what happens at the end of pagination, but for a list tool with strong annotations it is largely sufficient.

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 earns above that by explaining that the language and source filters must be carried forward with the cursor — a real interaction rule between 'after', 'language', and 'id' that the schema does not express. The legacy id=null note also adds meaning to the id parameter.

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 opens with a specific action and resource: finding saved audit prompts before generation. The word 'audits' implicitly scopes it apart from siblings like list_domain_fix_prompts and list_site_fix_prompts, though those siblings are never named, so differentiation requires inference from the title and description wording.

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?

It establishes a clear usage context ('before generation') and a usage rule for pagination ('Keep language and source filters when following the cursor'), which tells the agent how to continue paging correctly. It stops short of naming alternatives or stating when not to use this tool instead of get_fix_prompt or generate_fix_prompt.

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