Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

timesofisrael_news

Fetch Times of Israel top stories with no parameters, returning titles, URLs, and publication times for regular articles and liveblog updates.

Instructions

Get Times of Israel top stories. Returns the latest Times of Israel stories. It takes no parameters. Each item has a title, URL and publication time. The list includes both regular story pages and individual liveblog-update pages, so expect some entries to be short updates.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It helpfully discloses the return shape (title, URL, publication time) and a genuinely useful caveat that liveblog-update pages appear and may be short. It omits pagination, refresh/recency behavior, and any auth or rate-limit context, leaving meaningful gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening two sentences restate the same fact ('Get Times of Israel top stories' then 'Returns the latest Times of Israel stories'), which is redundant. The remaining two sentences (no params, item shape, liveblog caveat) are well front-loaded and earn their place.

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 parameterless news feed with no output schema, the description covers the return fields and a content caveat, which is reasonably complete. It still leaves the news-vs-headlines-vs-sections distinction unaddressed, which is the most important missing context given the many Times of Israel siblings.

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 and the description explicitly confirms 'It takes no parameters', so there is nothing further to document. Baseline 4 applies for a no-parameter tool.

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 clear verb and resource ('Get Times of Israel top stories' / 'latest Times of Israel stories'), so an agent knows exactly what it retrieves. However, it does not distinguish itself from close siblings like timesofisrael_headlines or timesofisrael_sections, which sound like they return overlapping content.

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?

There is no guidance on when to use this tool versus the sibling headlines/sections/article tools, and no mention of prerequisites or exclusions. 'Top stories' implies a default feed use, but the agent must infer that from the name alone.

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