Skip to main content
Glama

Crawlora MCP

by net.crawlora.mcp
OverviewDiscussionsAdmin

datasets_journalists_search

Read-only

Search the journalists dataset — public journalist/reporter contact records (outlet, title, beat topics, and any public work email or social handle) crawled from news outlets' own staff pages, for PR outreach.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoOptional full-text match on the journalist's name, title, and bio, max 256 characters.
pageNoResult page number, 1-based, default 1; page times page_size must not exceed 10000.
sortNoOptional sort order. Allowed values: relevance, name_asc, outlet_asc, crawled_desc, readiness_desc. Defaults to relevance with q, otherwise outlet_asc.
topicNoOptional exact topic filter, e.g. security, stablecoins. Use the values returned by facets?facet=topic.
outletNoOptional exact outlet filter, e.g. techcrunch, coindesk. Use the outlet ids returned by facets?facet=outlet.
verticalNoOptional exact beat-vertical filter. Allowed values: tech, crypto, marketing, consumer_tech, consumer_policy, cybersecurity, health, gaming, climate, business, entertainment, sports, legal, science, politics, real_estate, automotive, travel, food, education, design, film_tv, fashion, music, personal_finance, tech_independent, culture_independent, local_news, construction, banking, retail, aerospace_defense, energy, agriculture, local_business, general_news.
page_sizeNoPage size, default 20, max 100; page times page_size must not exceed 10000.
role_typeNoOptional role classification filter. Allowed values: staff, editor, reporter, contributor, freelancer, columnist, non_editorial, unknown.
email_kindNoOptional email semantics filter. Allowed values: individual_work, individual_personal_public, shared_desk, tips_or_submissions, outlet_generic, unknown.
record_typeNoOptional record classification filter. Allowed values: person, desk, organization, syndicated_byline, unknown.
contact_typeNoOptional exact contact-availability filter. Allowed values: email, social, none.
min_outreach_readinessNoOptional minimum outreach-readiness score from 0 to 100.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

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 readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful provenance context beyond that: the records are public, crawled from news outlets' own staff pages, which tells the agent to treat the data as scraped and public. It does not mention rate limits or result caps, but the schema handles pagination.

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?

A single front-loaded sentence that opens with the verb+resource and then adds qualifiers. Dense but every clause carries information; no filler.

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?

An output schema exists so return values need no explanation, and the schema fully documents parameters. The description supplies provenance, content scope, and intent, which is adequate for a 12-parameter read-only search tool. It could be stronger only in routing to sibling tools.

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%, so the schema already documents all 12 parameters including enums and defaults. The description loosely maps to a few filters (outlet, title, beat topics, email/social) but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb (Search) and resource (the journalists dataset) and even enumerates the record contents — outlet, title, beat topics, email/social. It clearly identifies what the tool returns, but it never distinguishes itself from its direct siblings datasets_journalists_facets and datasets_journalists_item.

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 trailing phrase 'for PR outreach' implies a usage context, and the schema references 'facets?facet=topic' for filter values. However the description itself gives no explicit when-to-use guidance, no exclusions, and no routing to the facets or item siblings — usage must be inferred.

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

All Crawlora MCP 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