Skip to main content
Glama

Read a company's site

web_crawl
Read-onlyIdempotent

Walk a company's own website and read up to twelve of its pages at once, the pages that say who the firm is and how to reach it first (team, people, leadership, about, contact). Returns each page's words and, across the pages, the e-mail addresses, phone numbers and people the site publishes, each with the page it is on. Use it to find who runs a firm and how to reach them when the database has no people or contacts for it. Members only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "web_crawl"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesA company's own site, as its address or its domain (acme.com). The walk starts there and stays on that site.
findNoWords to look for on each page, split with "|". Each page then comes back as the passages that hold them.
max_pagesNoHow many pages to read, 1 to 12. The pages that say who the firm is and how to reach it (team, people, leadership, about, contact) are read first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover readOnly, idempotent, openWorld, and non-destructive behavior. The description adds substantial context: a 12-page cap, priority ordering for team/contact pages, the exact extracted fields returned with page attribution, and an authentication requirement ('Members only').

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?

Three well-formed sentences that front-load the main action and then give return details and usage context. Slightly repetitive because the priority page list is repeated nearly verbatim in the max_pages schema description, but no sentence is wasted.

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?

No output schema exists, so the description carries the burden of explaining returns, which it does adequately by naming page text and extracted contacts. It covers the essential behavior, limits, and access requirement, though it does not address edge cases like inaccessible pages or rate limiting.

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%, so all three parameters are fully documented in the schema. The description reinforces the page limit and priority ordering but adds little meaning beyond the schema, and it does not mention the 'find' parameter at all.

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 ('walk ... and read') and resource ('a company's own website'), with scope ('up to twelve of its pages') and a clear return ('each page's words' plus extracted emails, phones, people). It implicitly distinguishes itself from generic web search/fetch by emphasizing the site stays on the company's own domain.

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 when-to-use condition: 'when the database has no people or contacts for it.' It does not name alternatives (e.g., web_fetch or web_search) or state when not to use it, but the context is strong enough for an agent to choose it correctly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources