Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jerusalempost_sections

Lists all 40 English-language editorial sections accepted by the Jerusalem Post headlines tool, including each section's slug, display name, and URL, so you can pick valid section filters.

Instructions

Get Jerusalem Post section inventory. Lists the 40 English-language editorial sections accepted by jerusalempost-headlines, such as world-news, israel-politics, archaeology and jewish-holidays. Each entry has a slug, display name and section url. Takes no parameters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does well: it discloses the fixed cardinality (~40 sections), that it takes no parameters, and the exact shape of each returned entry (`slug`, `name`, `url`). It doesn't mention auth or rate-limit behavior, but for a static read-only listing tool this is nearly complete disclosure.

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?

Three tight sentences, each earning its place: what it does, what the sections feed into with examples, and the return shape. Front-loaded with the purpose and free of padding.

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

Completeness5/5

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

Although there is no output schema, the description enumerates the returned fields, so an agent knows exactly what it will receive. For a zero-param listing tool this is fully complete.

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 tool takes zero parameters, so the baseline is 4. The description explicitly states 'Takes no parameters', reinforcing the empty schema and leaving nothing ambiguous.

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 and resource ('Get Jerusalem Post section inventory') and enumerates concrete examples (`world-news`, `israel-politics`, `archaeology`, `jewish-holidays`). It also distinguishes itself from the nearest sibling by naming `jerusalempost-headlines`, so an agent can tell the two apart without opening schemas.

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?

It frames the sections as those 'accepted by `jerusalempost-headlines`', which strongly signals the dependency: call this first to obtain valid section slugs. It stops short of an explicit when-to-use/when-not statement, but the linkage is clear enough for 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