Skip to main content
Glama
segentic-lab

periscope-mcp

by segentic-lab
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

test_project

Full-site audit: crawl all pages deterministically via sitemap, run chosen checks (visual, accessibility, SEO, etc.), and produce a JSON report with per-page issues, site-wide findings, auth status, and coverage comparison.

Instructions

Full-site audit: crawl every page (up to max_pages) and run the selected checks on each, saving a timestamped JSON report. The crawl is deterministic + sitemap-seeded, so consecutive runs cover the same pages and before/after comparisons are reliable (issue #22). Returns per-page issues, site-wide findings (e.g. duplicate titles/descriptions), an auth_check, pages_not_tested[] when the cap is hit, and a coverage delta (pages_added/pages_dropped) vs the previous report. Pages that bounce to the login page come back as auth_lost, never as fake success. Reload the saved report with get_report.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
checksNoTypes of checks to run
projectYesProject name
max_pagesNoOverride max pages. 0 = audit the WHOLE site (unbounded, stops at a 2000-page safety ceiling and flags ceiling_hit).
use_sitemapNoSeed the crawl from sitemap.xml / robots.txt when present (default: true). Set false for pure link-crawl.

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Details deterministic crawling, sitemap-seeding, return values including edge cases like auth_lost and pages_not_tested, and safety ceiling for max_pages=0.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences that front-load purpose and each sentence adds critical information without waste.

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?

Comprehensive for a tool with no output schema; covers purpose, parameters, return types, edge cases, and mentions related tool for reloading.

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 baseline 3; description adds value by explaining behavior like auth_lost and deterministic crawl, raising to 4.

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?

Clearly states 'Full-site audit' with specific verb 'crawl' and 'run checks', distinguishing from siblings like 'crawl_project' by emphasizing saving a report and deterministic behavior.

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?

Provides context for reliable before/after comparisons, but does not explicitly state when not to use or list alternatives beyond mentioning get_report.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/segentic-lab/periscope-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server