Skip to main content
Glama

get_article_content

Retrieve the complete text of a single Instapaper article by bookmark ID to analyze, summarize, or process its full content as plain text.

Instructions

Retrieve the complete text content of a single article. Use this to analyze, summarize, or process the full article text. Requires a bookmark ID. Returns the article as plain text.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bookmark_id": "<bookmark_id>"
    },
    "name": "get_article_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookmark_idYesID of the bookmark to fetch content for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

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 full burden. It does disclose the return format (plain text) and that a bookmark ID is mandatory, but says nothing about behavior when the ID is invalid, whether very long articles are truncated, or that the operation is a non-mutating read.

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 short sentences, front-loaded with the action and scoping, then usage and return format. The middle sentence is arguably the weakest but still short; nothing is padded.

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 simple single-parameter read tool with no output schema, the definition covers what it does, why to call it, the required input, and the return shape. Only edge-case behavior (missing ID, oversized article) is left unspecified, which is minor at this complexity.

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%, so the single bookmark_id parameter is already documented. "Requires a bookmark ID" merely restates the schema without adding format, range, or sourcing details, which is the expected baseline for a one-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?

"Retrieve the complete text content of a single article" gives a specific verb and resource, and the word "single" implicitly sets it apart from get_articles_content_bulk. It stops short of naming the bulk sibling directly, so the differential is inferred rather than stated.

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?

"Use this to analyze, summarize, or process the full article text" gives a use-case context, but there is no guidance on when to prefer this over get_articles_content_bulk when fetching multiple articles, and no stated preconditions beyond the ID requirement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.