Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_journalists_item

Retrieve a journalist's record by outlet ID and slug from the journalists dataset. Returns 404 if the outlet is unsupported or the journalist is not indexed.

Instructions

Get a journalist from the journalists dataset. Returns one journalist by outlet id and slug from dataset id enum value journalists. Returns 404 when the outlet is not supported or the journalist is not in the index.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesJournalist slug within the outlet, e.g. zack-whittaker
outletYesOutlet id, e.g. techcrunch. Use the ids returned by facets?facet=outlet

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It discloses the return type (one journalist) and error condition (404) but omits details like read-only nature, rate limits, or authentication. The transparency is adequate 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 with no redundant information. It directly states the action, the method, and error handling, making it efficient and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple get tool with two required parameters and no output schema, the description is mostly complete. However, it does not describe the structure of the returned journalist object, which could be helpful. The error handling is well-covered.

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?

Schema coverage is 100%, so the schema already documents both parameters. The description adds context by specifying the dataset enum value `journalists` and the need to use outlet ids from facets. This extra detail warrants a score above baseline.

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 it retrieves a journalist from a specific dataset using outlet id and slug. It distinguishes itself from sibling tools like datasets_journalists_search (search) and datasets_journalists_facets (facets) by being a singular get operation.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as datasets_journalists_search. The description only includes error handling information (404) but no usage context.

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

Deploy Server

Other Tools