Skip to main content
Glama
PROMPTEYE-SP-Z-O-O

prompteye-mcp

Official
by PROMPTEYE-SP-Z-O-O
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List the addresses in the connected sitemap

get_sitemap
Read-only

Fetch the active project's sitemap, its sync status, and listed addresses. Filter by active or dropped entries to compare with crawl data.

Instructions

The sitemap connected to the active project, how its last sync went, and the addresses it found — what the site says it wants read.

Each address carries path in the same form list_crawls reports, so the two can be compared: an address here with no crawl row is a page published into silence. active is false for an address that has dropped out of the sitemap while bots may still be asking for it.

sitemap is null when none is connected, and the list is then empty — a missing integration rather than an empty site. Sitemaps are connected in the PromptEye app. The first 5 000 addresses can be paged to.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many entries to return, at most 200. Defaults to 50.
activeNoOnly the addresses the sitemap still lists, or only those that dropped out of it.
cursorNoThe nextCursor of the previous page. Omit it to start from the first one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.16

TDQS

A4.3/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint already present, the description adds useful non-obvious behavior: sitemap can be null, active can be false for addresses that dropped out, and only the first 5,000 addresses are pageable. These details go beyond the annotations and help set expectations.

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 four purposeful sentences/fragments, front-loaded with the main purpose and then adding distinct facts: comparison to list_crawls, null semantics, and paging. It is slightly dense, but every clause earns its place.

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?

There is no output schema, so the description helps by covering the key returned concepts: path, active, null sitemap, and paging. It does not fully enumerate the sync-status fields or error cases, but an agent has enough to invoke the tool and interpret the important results.

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?

The input schema already documents all three parameters with 100% coverage, so baseline is 3. The description adds interpretive value by explaining what active=false means in context, how path relates to list_crawls output, and the 5,000-address paging boundary.

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?

The title and description name a specific verb + resource: list the addresses in the connected sitemap. The description also clarifies the scope (active project) and the value proposition (what the site says it wants read), distinguishing it from crawl-focused siblings like list_crawls.

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?

The description gives clear context for when this tool is relevant: inspecting the connected sitemap, comparing it to list_crawls output, and diagnosing a missing integration. It explicitly relates the data to list_crawls so an agent can choose between sitemap and crawl data, though it does not state a hard when-not to use it.

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