Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jerusalempost_headlines

Retrieve current Jerusalem Post section headlines by required slug, returning each story's title, URL, author, publication time, image, and summary when available.

Instructions

Get Jerusalem Post section headlines. Returns current Jerusalem Post stories for one section. section is required and takes one of 40 slugs such as israel-news, iran-news, middle-east, tech-and-startups or torah-portion. Each item has its title, URL, author, publication time and image, plus a summary except on premium items, which have none.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionYesJerusalem Post section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A3.5/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 and does disclose useful traits: the per-item shape (title, URL, author, publication time, image) and the notable caveat that premium items have no summary. It omits pagination, rate limits, or auth requirements, so it is helpful but not complete.

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?

Three front-loaded sentences: purpose, scope, then parameter and return details. No filler, though the slug examples duplicate the enum already present in the schema, adding mild redundancy.

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 one-parameter headlines tool with no output schema, the description supplies the return-field breakdown and the premium-item edge case, which is what an agent needs to interpret results. Missing pagination/limit info keeps it from being fully complete.

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?

The single `section` parameter is already fully documented in the schema at 100% coverage including the 40-value enum. The description repeats examples of slugs without adding format or selection guidance beyond what the schema lists, so it hits the baseline for high schema coverage.

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?

The description states a specific verb and resource ('Get Jerusalem Post section headlines') and bounds the scope to one section. It tells the agent exactly what is fetched, though it does not explicitly contrast itself with jerusalempost_news or jerusalempost_sections, so a sibling-routing discrimination is only implicit.

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?

Usage is implied: the agent learns it needs a section slug and gets representative examples. There is no explicit when-to-use-this-vs-alternatives guidance (e.g., headlines vs full news or article tools), so the agent must infer routing.

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