Skip to main content
Glama

instapaper_action

Manage Instapaper bookmarks: retrieve, add, archive, delete, or list folders using specified actions and credentials.

Instructions

Perform an Instapaper action: get_instapaper_bookmarks, add_instapaper_bookmark, archive_bookmark, delete_bookmark, get_instapaper_folders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
usernameNo
passwordNo
bookmark_idNo
urlNo
titleNo
folder_idNo
limitNo
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It fails to mention that delete_bookmark is destructive, that authentication is required, or any rate limits. The description only lists action names without behavioral context.

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?

The description is a single sentence that lists all possible actions. It is concise, to the point, and front-loads the key information. No extraneous words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 8 parameters and no output schema, the description is very incomplete. It does not cover authentication requirements, parameter dependencies for each action, or expected return values. The agent lacks critical context to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description should compensate. It only lists action names but does not explain the purpose or required values for parameters like username, password, bookmark_id, etc. Parameter names are somewhat self-explanatory, but the lack of any descriptions is insufficient.

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 clearly states the tool performs Instapaper actions and lists five specific actions (get_instapaper_bookmarks, add_instapaper_bookmark, etc.). The verb 'Perform' with the resource 'Instapaper action' is unambiguous. No sibling Instapaper tools exist, so differentiation is not an issue.

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?

The description provides no guidance on when to use the tool or how to choose among the listed actions. It does not mention prerequisites (e.g., authentication via username/password), nor does it describe conditions for using one action over another.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/malamutemayhem/unclick'

If you have feedback or need assistance with the MCP directory API, please join our Discord server