Skip to main content
Glama
Sign In

Feedly MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Save article to Board in Feedly

feedly_save_article_to_board
Read-onlyIdempotent

Save article to Board in the user's own Feedly account from ChatGPT, Claude or any AI agent. Returns how to do it in Feedly step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Feedly Cloud Browser. Feedly's official API: Feedly has a REST API, but only Enterprise clients can create a token, and its documented endpoints are built around Threat Intelligence (checked 17 Oct 2026).

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": "feedly_save_article_to_board"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

The description adds real substance beyond the annotations: it is a read-only guidance tool that returns instructions, opens nothing, and hands off execution to the browser tools. The API availability note explains why browser automation is required. It does not address failure modes (unknown board, article not open in browser), so it is not a 5.

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

Conciseness3/5

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

Purpose is front-loaded, but the opening 'from ChatGPT, Claude or any AI agent' is marketing filler and the closing API paragraph carries a dated 'checked 17 Oct 2026' aside that does not change how the tool is called. The core message could be delivered in about half the length.

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 zero-parameter tool with no output schema, the description should explain that the return value is a step-by-step procedure and what preconditions must hold (the article open in the Feedly Cloud Browser, the target Board existing). It covers the return nature but leaves those preconditions implicit.

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

Parameters4/5

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

With zero parameters there is no per-parameter semantics to explain, which is the baseline-4 case. However, the description never states how the tool knows which article and which Board to target, leaving the agent to infer that context comes from the browser session.

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 states the resource and goal (save an article to a Board in the user's own Feedly account) and then clarifies the actual deliverable: a step-by-step guide with screens, buttons and fields. A slight tension remains between the imperative-sounding name and the guidance-only behavior, but 'opens nothing by itself' resolves most ambiguity and separates it from the cotlet_browser_* tools.

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

Usage Guidelines4/5

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

It gives explicit sequencing guidance: call this first to get the procedure, then execute it with cotlet_browser_* tools. It also implies why not to use Feedly's REST API (token restricted to Enterprise, endpoints Threat-Intelligence oriented). No explicit when-not conditions are stated, so it stops short of a 5.

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

All Feedly MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources