Skip to main content
Glama

find_in_snapshot

Read-only

Searches the full page snapshot outline and returns matching lines under their ancestor refs, capped at 20 matches, to locate content on large pages without loading a full snapshot.

Instructions

Searches the whole 'snapshot' outline (never cut) and returns only the matching lines under their ancestors, with their refs (at most 20 matches). Cheaper than 'snapshot' on a large page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_in_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoText to find in the lines, case-insensitive. Give this or 'regex'.
regexNoJavaScript regular expression, case-sensitive. Give this or 'text'.
tab_idNoDefault: the active tab.
instance_idNoDefault: 'default'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-rc.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true), so the bar is lower, and the description still contributes real behavior: results are scope-limited to the full snapshot outline (never truncated), include ancestor context and refs, and are capped at 20 matches. The only gap is that it does not say what happens when more than 20 lines match (silent truncation vs. an indicator).

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?

Two dense sentences with no filler, and the essential scoping ('never cut', match cap) is front-loaded before the cost comparison. Slightly more compact phrasing could tighten the parenthetical, but nothing here wastes the reader's attention.

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?

With no output schema, the description carries the return-value burden and does so: matching lines, ancestor context, refs, and a 20-match cap. Combined with full schema coverage and a clearance annotation, an agent has what it needs to call this correctly; only the over-limit behavior is unspecified.

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 description coverage is 100%, with each of the four parameters documented in-schema, so the baseline of 3 applies and no additional parameter semantics are needed. The description adds no format or mutual-exclusivity detail beyond what the schema's 'Give this or regex' already says.

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?

States a specific verb (searches) and resource (the 'snapshot' outline), and pins down the exact output shape: only matching lines under their ancestors, with their refs. The closing clause explicitly contrasts it with the 'snapshot' sibling, so an agent can pick between them without opening either schema.

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?

Gives a clear selection rule against the sibling: it is 'cheaper than snapshot on a large page', which tells the agent when this tool is the better choice. It stops short of stating when NOT to use it (e.g., when a full outline is wanted), so it is strong context rather than a full when/when-not pair.

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