GTM for One

Preview outreach for a company

preview_outreach

Read-onlyIdempotent

Use when someone wants to know who might buy from a company, who its competitors are, or what a first cold email to a prospect could say. Give it the company website. It reads the public website and returns a preview: what the company sells, competitors, buyer segments, how many companies match, five example companies, and example email text. It is read-only for the user: it sends nothing, saves nothing to any account, and changes nothing anywhere; the example emails are text shown in the answer, not drafts in a mailbox. Takes up to a minute; if it is not finished, call continue_preview with the previewId it returns.

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": {
      "domain": "<domain>"
    },
    "name": "preview_outreach"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	The company website, for example acme.com or https://acme.com

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnly/destructive/idempotent annotations, it discloses that the tool reads the public website, sends nothing, saves nothing to any account, and that the example emails are answer text rather than mailbox drafts — a meaningful disambiguation for an outreach-themed tool. It also adds latency expectations ('up to a minute') and the continuation protocol, neither of which appears in the annotations.

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 the trigger condition, then the return contents, then the safety profile, then timing — a logical order with no filler. The return-contents sentence is a long comma-separated list that could be tightened slightly, which keeps it from a 5.

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?

For a single-parameter, no-output-schema tool, everything an agent needs is present: when to call, what input to supply, what comes back, that it is side-effect free, how long it takes, and what to do if it times out. No meaningful gap remains.

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% and the single parameter already documents the website format with examples, so the description's 'Give it the company website' adds only reinforcement. Baseline 3 applies when the schema carries the parameter burden.

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 names a specific verb and resource ('preview outreach' for a company) and enumerates exactly what the preview contains: what the company sells, competitors, buyer segments, match counts, five example companies, and example email text. That is far more specific than the title and lets an agent distinguish it from continue_preview, which only resumes an in-flight run.

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?

It gives explicit triggers ('who might buy from a company', 'who its competitors are', 'what a first cold email to a prospect could say') and states the required input ('Give it the company website'). It also routes the agent to the alternative when the run is unfinished: call continue_preview with the returned previewId.

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

All GTM for One tools Inspect

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

Need Help?