Skip to main content
Glama

agent_batch_convert

Convert up to 50 webpage URLs to clean Markdown in one call through signed-in Chrome, avoiding repeated single-URL calls; each result includes its own token count.

Instructions

The multi-URL form of agent_convert: up to 50 URLs in one call, each read through the user's signed-in Chrome. USE THIS instead of calling agent_convert in a loop — one call, one round trip, and each result carries its own token count. URLs are processed one after another, so a long list takes a while. Same requirements as agent_convert (Chrome + extension + native host).

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": {
      "urls": "<urls>"
    },
    "name": "agent_batch_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesArray of URLs to convert (max 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description does real work: it discloses sequential processing (so long lists are slow), single round trip, per-result token counts, and hard auth/setup requirements. It stops short of saying how partial failures or invalid URLs are handled, which matters for a batch tool.

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

Conciseness5/5

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

Front-loaded with the identity of the tool, then the routing instruction, then the caveats. Every clause adds decision-relevant information; nothing is redundant with the name.

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 one-parameter batch tool with no output schema, the description covers cost model, speed, prerequisites and result granularity. Missing only failure semantics (what happens when some URLs fail), which would round it out.

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 coverage is 100% and the single parameter already documents the array and the 50-item cap, so the description only confirms it. The statement that 'each result carries its own token count' hints at return shape rather than parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the specific verb+resource relationship precisely: 'the multi-URL form of agent_convert' with a cap of 50 URLs read via the signed-in Chrome. An agent can immediately tell this apart from the singular agent_convert and the other convert_* siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'USE THIS instead of calling agent_convert in a loop' gives an explicit alternative plus the condition that selects it, and the one-round-trip rationale explains why. The Chrome + extension + native host prerequisite mirrors agent_convert and closes the setup question.

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