Skip to main content
Glama
Sign In

Organiq GEO

by com.organiqgeo
OverviewDiscussionsAdmin

Pages affected by an audit issue

get_audit_issue
Read-onlyIdempotent

One issue code from the latest finished site audit: title, how to fix it, severity and the affected pages ordered by impressions of the last 28 days (url, HTTP status, depth, in sitemap, clicks, impressions). Codes come from get_site_audit (for example title_missing, broken_internal_link, noindex_with_clicks). Site-wide codes (robots_missing, sitemap_missing, llms_txt_missing, ai_bots_blocked, robots_blocks_audit) have no page list. Use it after get_site_audit to see which pages to fix for one issue. / Um problema da auditoria: título, correção e páginas afetadas por impressões.

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": {
      "site": "<site>",
      "code": "<code>"
    },
    "name": "get_audit_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesIssue code from get_site_audit.
siteYesProperty: displayName ("example.com"), Search Console siteUrl ("sc-domain:example.com", "https://www.example.com/") or numeric id. A unique substring among visible properties also works ("exam"). list_sites shows the options. The value "demo" selects a demonstration site with fictional data: it works without signing in and is read-only. / Propriedade por nome, siteUrl ou id; "demo" é um site de demonstração com dados fictícios, sem login e só leitura.
limitNoPages listed (default 25).
languageNoLanguage of issue titles and fixes (default en).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses the ordering rule (affected pages sorted by last-28-day impressions), implicitly the 28-day window, and the important behavioral edge case that site-wide issue codes yield no page list. It does not say what happens when no audit has finished yet or how large the page lists can get, which are the remaining behavioral gaps.

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 return shape and usage instruction are front-loaded, and each sentence carries information. The trailing Portuguese restatement of the purpose is redundant for an English reading agent and slightly dilutes an otherwise dense, well-structured definition.

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

Completeness5/5

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

There is no output schema, and the description compensates by enumerating the returned fields and their sort order. Combined with 100% schema coverage and read-only annotations, an agent has everything needed to select and call this tool correctly.

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 already 100%, but the description adds real meaning beyond it: it explains where the `code` enum values come from (get_site_audit) and gives concrete examples (title_missing, broken_internal_link, noindex_with_clicks), plus the semantic partition of codes that have no page list. `site` and `language` semantics are left to the schema, which is fine given its richness.

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 ('One issue code from the latest finished site audit') and enumerates exactly what is returned: title, fix, severity, affected pages with url/status/depth/in-sitemap/clicks/impressions. It is clearly distinguishable from get_site_audit, which it names as the source of the codes.

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?

'Use it after get_site_audit to see which pages to fix for one issue' gives an explicit sequencing rule and intent, so the agent knows this is the drill-down step rather than the audit summary. It also carves out the exception set (site-wide codes such as robots_missing, sitemap_missing, ai_bots_blocked) that return no page list, which prevents a wrong expectation.

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

All Organiq GEO 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