Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

datasets_journalists_search

Search a curated database of journalists and reporters from news outlets, filtered by beat, outlet, or contact type, to find relevant contacts for PR outreach.

Instructions

Search the journalists dataset. Searches the journalists index (dataset id enum value journalists) — public journalist and reporter contact records crawled from news outlets' own staff/author pages, for PR outreach. Each record carries the outlet, title, best-effort beat topics, and any public contact info (a work email or a social handle) found on that outlet's own page. There is no cross-outlet upstream search; this dataset is built by crawling a curated roster of outlets ourselves. vertical enum: tech, crypto, marketing, consumer_tech, consumer_policy, cybersecurity, health, gaming, climate, tech_independent, culture_independent. contact_type enum: email, social, none. sort enum: relevance, name_asc, outlet_asc, crawled_desc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text match on the journalist's name, title, and bio, max 256 characters
pageNoPage number, defaults to 1
sortNoSort enum: relevance, name_asc, outlet_asc, crawled_desc
topicNoExact topic filter, e.g. security, stablecoins. Use the values returned by facets?facet=topic
outletNoExact outlet id filter, e.g. techcrunch, coindesk. Use the ids returned by facets?facet=outlet
verticalNoExact beat-vertical filter. Enum: tech, crypto, marketing, consumer_tech, consumer_policy, cybersecurity, health, gaming, climate, tech_independent, culture_independent
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
contact_typeNoContact-availability filter. Enum: email, social, none
Behavior4/5

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

Despite no annotations, the description discloses the data origin (crawled from outlets' staff pages), record fields, and limitation (no cross-outlet search), providing good transparency about what the tool does and its constraints.

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 description is a single, fairly long paragraph but all information is relevant and front-loaded with the purpose. It could be slightly more structured, but is concise overall.

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?

Given 8 optional parameters and no output schema, the description covers key aspects: purpose, data fields, filter enums, and dataset limitations. It lacks return format details but compensates with field descriptions.

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?

The description adds value by listing enum values for sort, vertical, and contact_type, and by noting that topic and outlet filters use facet endpoints, going beyond the schema's parameter descriptions.

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 clearly states the tool searches a journalists dataset for PR outreach, specifies the data source and fields, and distinguishes it from sibling tools like datasets_journalists_facets by focusing on search.

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?

The description explains the dataset scope (curated outlets, no cross-outlet search) and suggests use for PR outreach, but does not explicitly contrast with other sibling tools or provide explicit when-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Crawlora-org/crawlora-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server