Skip to main content
Glama

tap_run

Run a pre-built tap to extract structured data from a site. Returns rows, columns, and timing; results are cached for 5 minutes to avoid redundant calls.

Instructions

Run a pre-built tap. Preferred over tap.* tools — deterministic, zero AI at runtime. Returns {columns, rows, count, timing, cache_hit}. Read-intent taps are memoized for 5 minutes per process; identical calls return cached data with cache_hit:true. Pass {fresh:true} to bypass cache. Write-intent taps are never cached. If rows contain login/error page content or are empty on a site that requires login → call tap.runtime(runtime:'chrome') first, then retry. If rows is empty on a public site, use tap.doctor(site, name) for structured diagnosis. On transient failure (timeout, connection), RETRY tap.run — do not fall back to manual tap.* operations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYesSite name
nameYesTap name
argsNoTap arguments
freshNoBypass the 5-minute per-process result cache. Use when you need current data despite a recent identical call.
envelopeNoResponse shape. 'bare' (default) returns {rows, columns, count, elapsed_ms}; 'annotation' wraps the result in a W3C Web Annotation with target + body:tap:RunResult + prov:wasDerivedFrom — useful for provenance chains and signing. Does NOT affect sub-tap composition or pipe bindings (those read the internal flat shape).bare
Behavior5/5

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

The description adds significant behavioral context beyond annotations: read-intent taps are memoized for 5 minutes, identical calls return cached data with cache_hit:true, fresh:true bypasses cache, write-intent taps never cache, and error handling for login/error pages and transient failures. Annotations are readOnlyHint=false, destructiveHint=false, openWorldHint=true, and description does not contradict them.

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 appropriately sized, front-loads the core purpose, and every sentence serves a purpose: stating purpose, caching behavior, error handling, and retry logic. No redundant content.

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?

Given 5 parameters, full schema coverage, sibling tools, and absence of output schema, the description covers return shape ({columns, rows, count, timing, cache_hit}), caching behavior, error recovery mechanisms, and when to use sibling tools. It is complete and self-contained.

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 is 3. The description adds value by explaining fresh:true bypasses cache, envelope parameter differences between 'bare' and 'annotation', and implicit context for site and name. While schema already describes parameters, the description clarifies their behavioral impact.

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 clearly states the tool runs a pre-built tap, emphasizes it is preferred over tap.* tools, and distinguishes sibling tools by highlighting deterministic behavior with zero AI at runtime.

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 provides explicit usage guidance: when to use this tool, when to use fresh:true to bypass cache, when to fall back to tap.runtime for login/error pages, when to use tap.doctor for empty rows on public sites, and how to handle transient failures by retrying tap.run. It also specifies caching rules and alternatives.

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/LeonTing1010/tap'

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