Skip to main content
Glama

Heista

by co.heista
OverviewDiscussionsAdmin

Fleet — Site Pages Inventory

fleet_site_pages
Read-onlyIdempotent

Filterable inventory of every sitemap-listed page with SEO facts (title, meta description, canonical, h1, word count, JSON-LD) and internal inlink/outlink counts from the weekly crawl. Filters: path_contains, orphans_only (zero inlinks), max_word_count (thin content), status, missing_meta. Sorted fewest-inlinks first — the pages Google cannot discover float to the top. Hard cap 100 rows. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax rows (default 25, hard cap 100).
offsetNoPagination offset.
statusNoFilter by HTTP status (e.g. 200, 308, 404).
path_prefixNoFilter: path STARTS WITH this (e.g. "/creative/library"). Anchored — prefer this. Filtering /creative by substring returns 77 pages; by prefix, 9.
missing_metaNoOnly pages missing a meta description.
orphans_onlyNoOnly pages with ZERO internal inlinks — the pages Google has no path to discover.
path_containsNoFilter: path contains this anywhere. Over-matches — "/creative" also returns /creative-playbooks and /creative-development. Use path_prefix unless a substring is genuinely wanted.
max_word_countNoOnly pages at or below this visible word count (thin-content filter, e.g. 150).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / path_contains / description
      Previous value: -"Filter: path contains this anywhere. Over-matches — \"/creative\" also returns /creative-playbooks and /for/creative-strategists. Use path_prefix unless a substring is genuinely wanted."New value: +"Filter: path contains this anywhere. Over-matches — \"/creative\" also returns /creative-playbooks and /creative-development. Use path_prefix unless a substring is genuinely wanted."
  2. Changed2 schema fields changed
    • changedInput schema / properties / path_contains / description
      Previous value: -"Filter: path contains this string (e.g. \"/decode/\", \"/intelligence\")."New value: +"Filter: path contains this anywhere. Over-matches — \"/creative\" also returns /creative-playbooks and /for/creative-strategists. Use path_prefix unless a substring is genuinely wanted."
    • addedInput schema / properties / path_prefix
      Added value: +{
+  "description": "Filter: path STARTS WITH this (e.g. \"/creative/library\"). Anchored — prefer this. Filtering /creative by substring returns 77 pages; by prefix, 9.",
+  "maxLength": 200,
+  "type": "string"
+}
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark the tool read-only, and the description adds valuable behavioral context: data is from the weekly crawl, results are sorted fewest-inlinks first, and there is a hard cap of 100 rows. It also explicitly states 'Read-only,' reinforcing the annotation without contradiction.

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?

Purpose, scope, included fields, filters, sort behavior, row cap, and read-only status are all conveyed in a compact, front-loaded description. Every clause adds useful information with no filler or repetition.

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?

Even without an output schema, the description enumerates returned SEO facts and link counts, filter options, sort order, data freshness, and row cap. Combined with the fully described input schema, an agent has enough context to select and invoke this tool correctly.

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

Parameters3/5

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

Schema coverage is 100% with detailed per-parameter descriptions, so the description carries a low burden here. The listed filters mirror the schema and add no meaning beyond it, though it does tie orphans_only and max_word_count to their SEO intent, which the schema also already does.

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 description opens with 'Filterable inventory of every sitemap-listed page' and enumerates the exact SEO fields and link counts returned, giving a very specific resource and scope. It distinguishes itself from sibling tools like fleet_site_links and fleet_gsc_top_pages by grounding the data in sitemap pages and crawl-derived SEO metrics.

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?

Clear context is provided: this is the tool for a filterable sitemap page inventory with SEO diagnostics, and the sort note explicitly surfaces orphan/low-inlink pages for discovery work. It does not explicitly name when-not-to-use cases or alternative tools, so it stops short of a 5.

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

All Heista 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