Skip to main content
Glama

Heista

by co.heista
OverviewDiscussionsAdmin

Fleet — AI Crawler Hits

fleet_crawler_hits
Read-onlyIdempotent

Server-logged crawler fetches: which AI engines (GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, …) and search crawlers (Googlebot, Bingbot) fetched which heista.co pages, and when. This signal is invisible to page analytics — crawlers never run the tracking script. Group by bot, page, or date; filter by bot or path. Logging began 2026-07-23 (no earlier history exists). 180-day retention. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
botNoFilter to one bot (canonical names: gptbot, oai-searchbot, chatgpt-user, claudebot, claude-user, perplexitybot, perplexity-user, googlebot, bingbot, …).
daysNoWindow in days (default 28, max 180 — retention limit).
limitNoMax rows (default 25, hard cap 100).
group_byNoAggregation: by bot (default — which engines are crawling), by page (what they fetch), or by date (crawl cadence).
path_prefixNoFilter: page path STARTS WITH this (e.g. "/creative/library"). Anchored — this is the one you want. Prefer it over path_contains.
path_containsNoFilter: page path contains this anywhere. Over-matches — "/creative" also returns /creative-playbooks and /creative-development. Use path_prefix unless you deliberately want a substring.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / path_contains / description
      Previous value: -"Filter: page path contains this anywhere. Over-matches — \"/creative\" also returns /creative-playbooks and /for/creative-strategists. Use path_prefix unless you deliberately want a substring."New value: +"Filter: page path contains this anywhere. Over-matches — \"/creative\" also returns /creative-playbooks and /creative-development. Use path_prefix unless you deliberately want a substring."
  2. Changed2 schema fields changed
    • changedInput schema / properties / path_contains / description
      Previous value: -"Filter: page path contains this string (e.g. \"/decode\", \"/intelligence\")."New value: +"Filter: page path contains this anywhere. Over-matches — \"/creative\" also returns /creative-playbooks and /for/creative-strategists. Use path_prefix unless you deliberately want a substring."
    • addedInput schema / properties / path_prefix
      Added value: +{
+  "description": "Filter: page path STARTS WITH this (e.g. \"/creative/library\"). Anchored — this is the one you want. Prefer it over path_contains.",
+  "maxLength": 200,
+  "type": "string"
+}
  3. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds meaningful behavioral context: the data is server-logged and invisible to page analytics because crawlers never run the tracking script. It also discloses the retention limit (180 days) and the logging start date, which are behavioral constraints an agent needs to know. The only minor gap is that it doesn't describe the exact output shape, but with no output schema and read-only annotations, the description carries the burden well.

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?

The description is compact and front-loaded: the first sentence states exactly what the tool returns, the second explains why this data matters, and the third gives usage guidance. Every sentence earns its place, and the retention/logging-start facts are packed efficiently. No fluff or repetition of schema details.

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?

For a read-only, filterable list tool with 100% schema coverage and no output schema, the description is complete. It covers what the tool returns, why it's useful, how to group/filter, and the temporal constraints (start date, retention). An agent has everything needed to decide whether to call it and how to set parameters 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 description coverage is 100%, so the schema already documents all six parameters thoroughly. The description adds value by explaining the conceptual grouping ('Group by bot, page, or date') and the filtering dimensions ('filter by bot or path'), which maps directly to the group_by and path_prefix/path_contains parameters. It also reinforces the retention limit that constrains the days parameter. The description doesn't repeat parameter-level details, which is appropriate given the schema's completeness.

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 states a specific verb ('fetched'), a precise resource (server-logged crawler fetches of heista.co pages), and the key actors (AI engines and search crawlers). It also distinguishes this signal from page analytics, which helps an agent understand exactly what data this tool exposes. The title and description together clearly differentiate it from sibling analytics tools like fleet_analytics_overview or fleet_gsc_top_pages.

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?

The description explicitly says when to use this tool: when you need crawler fetch data that is invisible to page analytics. It also provides concrete grouping and filtering guidance ('Group by bot, page, or date; filter by bot or path'). The retention and logging-start constraints ('Logging began 2026-07-23', '180-day retention') give clear temporal boundaries for when this tool is applicable. It doesn't name a specific alternative, but the context is clear enough that an agent can select it appropriately among the many fleet_* siblings.

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