Skip to main content
Glama

get_articles_content_bulk

Fetch the full text of multiple articles at once by bookmark IDs to support bulk analysis, cross-source comparison, and comprehensive research.

Instructions

Fetch the complete text of multiple articles simultaneously for efficient bulk analysis. Provide an array of bookmark IDs. Articles are retrieved in parallel for best performance. Each article is returned with its ID, content, or error status. Ideal for synthesizing information across multiple sources, comparing perspectives, or comprehensive research analysis.

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_ids": "<bookmark_ids>"
    },
    "name": "get_articles_content_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookmark_idsYesArray of bookmark IDs to fetch content for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 useful behavior such as parallel retrieval and that each article returns either content or an error status, which signals partial-failure tolerance. It omits permission/auth requirements, rate limits, maximum array size, and whether content is raw HTML or cleaned text.

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?

It is front-loaded with the core action and input requirement, then return behavior, then use cases. There is mild redundancy between 'for efficient bulk analysis' and 'parallel for best performance', and the closing use-case sentence is marketing-flavored but still informative.

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 one-parameter read tool with no output schema, the description covers input and the general return shape. It leaves open batch size limits, error-status semantics, and content format, which matter for an agent planning a bulk fetch.

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?

The single parameter has 100% schema description coverage, so the schema already documents 'Array of bookmark IDs to fetch content for'. The description restates the same idea without adding format, limits, or ordering semantics, 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?

The description gives a specific verb and resource ('Fetch the complete text of multiple articles') and scopes it to bulk use ('simultaneously'), which implicitly separates it from the single-article sibling get_article_content. It stops short of naming that sibling explicitly, so the differentiation 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?

Usage is framed by intent ('synthesizing information across multiple sources, comparing perspectives, or comprehensive research analysis'), which implies when the tool fits. However, there is no guidance on when to use the single-article tool instead, no batch-size limits, and no stated conditions or exclusions.

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