Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jerusalempost_author

Fetch a Jerusalem Post author or blogger profile by canonical /author/ or /blogger/ URL. Returns name, bio, image, and article cards in JSON.

Instructions

Get Jerusalem Post author profile. Returns a Jerusalem Post author or blogger profile by url, a canonical /author/<slug> or /blogger/<slug> link. The response has the profile type, name, description, image_url and article cards with title, URL, summary and publication time.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Jerusalem Post /author/<slug> or /blogger/<slug> profile URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

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 behavioral burden. It discloses the return shape (profile type, name, description, image_url, article cards) which is genuinely useful since no output schema exists, but says nothing about auth requirements, rate limits, or error/empty behavior.

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?

Two tight sentences, front-loaded with the action and then the accepted URL forms and return contents. It is appropriately sized; the minor repetition of 'Jerusalem Post' is not wasteful enough to penalize heavily.

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 single-parameter profile fetch with no output schema, the description supplies the return fields and accepted URL formats, which is enough for correct invocation. Only the absence of usage/alternative routing guidance keeps 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% and the single `url` param is fully documented in the schema. The description's mention of '/author/<slug>' and '/blogger/<slug>' largely duplicates the schema text, adding little beyond it, so the baseline 3 applies.

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 specific verb+resource ('Get Jerusalem Post author profile') and clarifies it returns an author OR blogger profile keyed by a canonical /author/<slug> or /blogger/<slug> link. It is clearly distinct from jerusalempost_authors by being singular and URL-keyed, but it never explicitly names the sibling list tool, so it stops short of full differentiation.

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 when-to-use guidance, no prerequisite statement, and no reference to an alternative. The agent must infer from the name that this fetches a single profile rather than listing authors (jerusalempost_authors) or reading an article (jerusalempost_article).

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