Skip to main content
Glama
Sign In

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. Costs 1 credit per record returned (minimum 2), so keep page_size to what you need.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "datasets_journalists_search"
  }
}

Input 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

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

A4.2/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 safety is covered. The description adds genuinely non-obvious behavior: a credit cost of 1 per record with a 2-record minimum, which materially affects call strategy. It does not describe pagination edge cases or result shape, but the cost disclosure is a strong addition beyond structured fields.

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?

Two tight sentences: identity/scope first, cost second. Every clause earns its place and the most important constraint (what the tool is) is front-loaded.

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 12 fully documented params, an output schema, and annotations, the description covers the essentials an agent needs. It slightly underplays the facet-driven workflow for discovering topic/outlet filter values, which the schema mentions but the description omits, keeping it from a 5.

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% (all 12 params, including allowed enum values, are documented in the schema). The description only references page_size in a cost context; it adds no syntax or semantics beyond what the schema already provides, so the baseline of 3 applies.

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?

States a specific verb (Search) and resource (the journalists dataset), then enumerates the record contents (outlet, title, beat topics, email/social handle) and provenance (crawled from outlets' own staff pages). An agent can immediately tell this apart from datasets_journalists_item (single record) and datasets_journalists_facets (facet values) without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear usage context ('for PR outreach') and actionable cost-aware advice ('keep page_size to what you need'). However, it names no alternatives and gives no when-not guidance, so it stops short of the explicit routing a 5 would require.

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