Skip to main content
Glama
Sign In

UnblockingAPI

by io.github.unblockingapi
OverviewDiscussionsAdmin

Find a structured-data template

find_templates
Read-onlyIdempotent

Find published templates that parse a site into structured JSON instead of HTML. Pass the url you are about to fetch to see whether one already covers it — do this before writing your own extraction for a well-known site. Also searches by keyword or category. Each result shows the fields it returns and an example call; pass its reference as unblock_fetch's template argument. Free — no credit is charged.

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_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA URL you intend to fetch. Returns the templates built for that site, if any.
pageNoWhich page of `limit` results to return, from 1, when more templates match than fit.
limitNoMaximum templates to return (default 25).
searchNoKeyword matched against a template's name, reference, host and description (e.g. 'property', 'company').
categoryNoCategory slug, e.g. 'search-results', 'real-estate', 'business-directories'. Omit all filters to see the categories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / page
      Added value: +{
+  "description": "Which page of `limit` results to return, from 1, when more templates match than fit.",
+  "minimum": 1,
+  "type": "integer"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds valuable non-schema behavior: the call is free and charges no credit, and each result surfaces the fields returned plus an example call. It doesn't cover pagination limits or result caps beyond what the schema implies.

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?

Four dense sentences, front-loaded with the core purpose before the usage instruction and the cost note. Every sentence carries information, though the keyword/category sentence is slightly tacked on and could fold into the surrounding text.

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?

With no output schema present, the description steps in to describe what a result contains (fields and an example call) and how to use it downstream. Combined with the safety annotations and the 100%-covered parameter schema, an agent has everything needed to select and invoke this tool.

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 the baseline is 3, but the description adds genuine semantic value beyond the schema by explaining the intent behind the url filter (check coverage before you fetch) and the cross-tool meaning of a result's template reference. It says less about page/limit semantics, which the schema already documents.

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 and resource ('Find published templates') plus the distinctive outcome ('parse a site into structured JSON instead of HTML'), which separates it from a generic search tool. It also implicitly contrasts with the sibling unblock_fetch by naming what to do with a template reference.

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?

Explicitly instructs when to use it ('Pass the url you are about to fetch', 'do this before writing your own extraction for a well-known site') and sequences it against the sibling tool by telling the agent to pass a result's reference as unblock_fetch's template argument. No exclusions are left to inference.

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

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