Skip to main content
Glama

inoreader_open

Open a signed-in Inoreader page in Cloud Browser to manage read articles, organize feeds, and create rules.

Instructions

Open a Inoreader page in your signed-in Cloud Browser (default https://www.inoreader.com) to work with read articles, organize feeds and create rules.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inoreader_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://www.inoreader.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.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 usefully discloses that the browser is 'signed-in' (an auth/session requirement) and supplies the default target, but says nothing about whether it navigates away from an existing page, whether it returns page content, or whether the session persists for follow-up calls.

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?

A single front-loaded sentence with no filler; the verb and default come first and the use cases trail. Minor deduction for the grammatical slip 'a Inoreader' and for packing default and purpose into one dense clause.

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-optional-parameter navigation tool with no output schema and no annotations, the description covers the essentials: what opens, where, and under what session state. The main gap is what the agent should expect after opening (return value or session handoff), which is minor here.

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?

Only one optional parameter exists and schema coverage is 100%, so the schema already documents it fully. The description merely repeats the same default URL value, adding no new syntax, format, or constraint information beyond the schema.

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?

States a specific verb and resource: 'Open a Inoreader page in your signed-in Cloud Browser', with the default URL inline. It also names the downstream goals (read articles, organize feeds, create rules), which separates it from siblings like inoreader_click or inoreader_read, though it never explicitly contrasts with them.

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 implied through the purpose clause ('to work with read articles, organize feeds and create rules'), giving the agent a sense of when to start here. It does not say when not to use it, nor does it point to the sibling tools (click/type/read/close) that presumably follow an open.

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