Fetch a Jerusalem Post author or blogger profile and its article cards from a canonical /author/ or /blogger/ URL. Use it to turn public profile pages into structured JSON.
Get Jerusalem Post author profile. Returns a public author or blogger profile and article cards from its first-party profile page.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical Jerusalem Post /author/<slug> or /blogger/<slug> profile URL |
Changes observed during successful MCP inspections.
v1.17.7Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It does disclose that it returns a public profile (author or blogger) plus article cards from a first-party page, which is useful, but says nothing about auth, rate limits, or behavior on invalid URLs.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences with the core action front-loaded and the return content secondary. No filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-param read tool with no output schema, the description states both the input expectation and the returned content. Only the relationship to the sibling author-list tool is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the schema already documents the canonical /author/<slug> or /blogger/<slug> URL format. The description's mention of "author or blogger profile" mirrors the schema without adding new semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gives a specific verb+resource ("Get Jerusalem Post author profile") and clarifies it returns a profile plus article cards. It implicitly separates itself from jerusalempost_authors (which lists authors), but never names or contrasts that sibling explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this versus jerusalempost_authors or jerusalempost_article, and no prerequisites stated. The only hint is that it takes a profile URL, which is inferred rather than given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.