Skip to main content
Glama

SteadyScrape Company Data

Company profile from its website

company_profile
Read-only

Reads 1-10 company websites (homepage plus about/contact pages) and returns per domain: company and legal name, description, industry guess, address when published, founded year and stated employee count when published, logo, company social pages (LinkedIn, X, Facebook, Instagram, YouTube, GitHub), detected website technologies and language. No email addresses or phone numbers. Billed per profile returned.

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": {
      "domains": "<domains>"
    },
    "name": "company_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYes1-10 company domains or website URLs, e.g. stripe.com or https://www.notion.so.
pages_per_domainNo1 = homepage only (fastest); 3 = + about and contact pages (default); 4 adds the imprint page; 5 also tries /company.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, open-world behavior, so the description's marginal contribution is the cost model ('Billed per profile returned') and the batch cap of 1-10, both of real operational value for planning a call. It stops short of explaining failure handling for unreachable or non-company domains.

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?

The core action and cost caveat are front-loaded in a single dense sentence, with the field list reading as a compact return contract. The enumeration is long but each item carries information, so there is minimal waste.

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 appropriately serves as the return-value contract by listing every returned field and the exclusions. Combined with annotations and full schema coverage, an agent has enough to call it correctly; only error/partial-failure behavior is unaddressed.

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% and both parameters are documented in the schema, including the per-value meaning of pages_per_domain, so the baseline is 3. The description only echoes that the crawl covers homepage plus about/contact pages, adding little beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb ('Reads') and resource ('1-10 company websites') and then enumerates the exact fields returned per domain, so an agent knows precisely what the tool produces. It does not name or contrast with siblings like sites_using_technology, so routing between the two depends on the agent's own inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the shape of the input (supply domains, get profiles), and the 'No email addresses or phone numbers' line usefully sets expectations on scope. However, there is no explicit when-to-use/when-not guidance and no pointer to an alternative tool when the agent needs contact data or technology-only lookups.

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