Skip to main content
Glama

Salesbot - B2B outreach LinkedIn MCP Server with CRM and email

by cz.salesbot
OverviewDiscussionsAdmin

read_company_website

Read-onlyIdempotent

Read a company's own public website for a short company profile: title, description, main headings and a short text excerpt per page, each with its source URL, plus generic company e-mails (info@, obchod@, sales@ …) and linkedin_company_pages – the company's LinkedIn page linked from its own site (pass it to search_linkedin_people as companyLinkedInUrl). Pass the company's homepage (or a page on it); the tool also reads up to 3 standard pages linked from it (contact, about, services) on the same host – it never crawls further or leaves the site. Personal e-mail addresses and phone numbers are masked; no employee lists are collected. Sites that block bots (robots.txt, noindex / noai, TDM reservation), need a login, show a CAPTCHA or a paywall are skipped, not worked around. Limit: 60 reads per account per day. Nothing is stored – save what matters with update_company_research (with the source URLs). A generic e-mail found here is NOT consent to contact: never add it to outreach automatically; the user decides.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe company's own homepage or a page on its website, e.g. https://www.firma.cz. Never a LinkedIn or social-network URL (pass a LinkedIn company page to search_linkedin_people as companyLinkedInUrl).
extra_urlsNoOptional: up to 3 specific pages on the same website to read instead of auto-picked contact/about/services pages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"The company's homepage or a page on its website, e.g. https://www.firma.cz"New value: +"The company's own homepage or a page on its website, e.g. https://www.firma.cz. Never a LinkedIn or social-network URL (pass a LinkedIn company page to search_linkedin_people as companyLinkedInUrl)."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare the safe read-only profile, yet the description adds real behavioral context beyond them: personal e-mails and phone numbers are masked, no employee lists collected, crawl depth capped at 3 standard pages on the same host, bot-blocked/noindex/TDM sites are skipped rather than worked around, a 60-reads-per-day limit, and nothing is persisted.

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?

Front-loaded with purpose and return contents, and every clause carries information (masking, limits, routing). It is a dense single paragraph rather than cleanly segmented, which slightly hurts scanability.

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?

No output schema exists, but the description enumerates the returned fields and their shape (per-page excerpt with source URL, generic e-mails, linkedin_company_pages). With annotations plus a 100%-documented 2-param schema, an agent has everything needed to call it correctly.

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, but the description goes further by clarifying the url must be the company's own site and that extra_urls replaces the auto-picked contact/about/services pages by naming those defaults and the same-host constraint.

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?

Names a concrete verb (read) and resource (a company's own public website) and enumerates exactly what it extracts: title, description, headings, excerpt, source URL, generic e-mails and linkedin_company_pages. It is clearly distinguishable from sibling readers like search_linkedin_people or search_web.

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 states what to pass (the company homepage or a page on it, never a LinkedIn/social URL), routes LinkedIn URLs to search_linkedin_people as companyLinkedInUrl, and points to update_company_research for persistence. When-not conditions are covered via blocked/login/CAPTCHA/paywall sites.

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

All Salesbot - B2B outreach LinkedIn MCP Server with CRM and email 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