Skip to main content
Glama
Sign In
Semrush MCP

Semrush MCP

by mrkooblu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

semrush_site_audit_pages

Read-onlyIdempotent

List pages from a site audit using project ID and URL, with optional pagination via limit and page parameters.

Instructions

List pages from a site audit

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": {
      "project_id": "<project_id>",
      "url": "<url>"
    },
    "name": "semrush_site_audit_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
urlYes
limitNo
pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows it's safe. However, the description adds no additional behavioral context such as rate limits, pagination behavior, or what happens if the project_id or url is invalid. Without any extra information, the description fails to enhance transparency beyond annotations.

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 extremely concise at 5 words, which makes it quick to read. It front-loads the verb 'List'. However, given the number of parameters and the existence of sibling tools, a slightly more detailed description would be beneficial without sacrificing conciseness.

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

Completeness2/5

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

The tool has 4 parameters and no output schema, yet the description provides no information about output format, required inputs, or behavior. The annotations cover safety but not functional behavior. The description is incomplete for an agent to effectively call this tool without additional schema inspection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning no parameter has a description in the schema. The tool description also does not explain any parameters (project_id, url, limit, page). For a tool with 4 parameters, this is a critical gap. The agent has no guidance on what each parameter does, especially the optional ones like limit and page.

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 clearly states the verb 'List' and the resource 'pages from a site audit', making the basic purpose obvious. However, it does not differentiate from sibling tools like semrush_site_audit_page_detail or semrush_site_audit_issues, which might also involve pages. A more distinct description would improve clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. For example, it does not explain that this lists all pages from a specific audit snapshot, nor does it mention prerequisites like having an existing audit. The description simply states what it does without context.

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

Deploy Server

Other Tools