Skip to main content
Glama

Copy a research's instant audience into a search

sdr_materialize_research

Copies the instant audience of a finished research into a search as contacts (background, idempotent, filtered by the search's regions/cities). sdr_create_search with research_job_id already does this after activation; use this only to repeat it. Contacts are billed (5 credits each, 10 from hunters on paid data) like any other contact when used.

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": {
      "job_id": "<job_id>",
      "search_id": "<search_id>"
    },
    "name": "sdr_materialize_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
search_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and discloses key traits: background execution, idempotency, filtering by the search's regions/cities, and billing at 5 credits per contact (10 for hunter contacts on paid data). It does not disclose permission requirements, rate limits, or what the response looks like, so it is strong but not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences, front-loads the core purpose and distinguishing behavior, then adds the sibling comparison and billing caveat. Every sentence adds useful information with no repetition.

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?

For a two-parameter copy operation with no output schema and no annotations, it covers the critical context: what is copied, that it runs in the background, idempotency, filtering scope, billing, and when to use it instead of sdr_create_search. It omits explicit parameter naming and permission prerequisites, but is otherwise sufficient for invocation.

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 0%, so the description must compensate for two required UUID parameters. It implicitly maps job_id to a finished research and search_id to the target search, and mentions filtering by the search's regions/cities, but it never names the parameters or explains their format or requiredness explicitly.

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 uses a specific verb and resource: it copies a finished research's instant audience into a search as contacts. It also explicitly distinguishes this from sdr_create_search, which already performs the same copy during activation, leaving no ambiguity about what the tool does.

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 states when to use this tool versus the sibling: sdr_create_search with research_job_id already copies the audience after activation, so this tool is only for repeating that operation. This is an explicit when/when-not rule with the alternative named.

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