Skip to main content
Glama
Sign In

Google Discover MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Read Discover feed in Google Discover

google_discover_read_discover_feed
Read-onlyIdempotent

Read Discover feed in the user's own Google Discover account from ChatGPT, Claude or any AI agent. Returns how to do it in Google Discover step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Google Discover Cloud Browser. Google Discover's official API: Google Discover has no API for the feed (checked 25 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": "google_discover_read_discover_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: the call opens nothing by itself, it returns screen/button/field steps, and Google Discover offers no official feed API (checked 25 Oct 2026) - context an agent cannot get from structured fields.

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?

The core point (returns steps, does not act) is stated early, but the text is padded with marketing phrasing ('from ChatGPT, Claude or any AI agent'), repeated 'Google Discover' mentions, and a stale dated API aside that reads as boilerplate. Trimming would sharpen it without losing information.

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 zero-parameter, no-output-schema tool, the definition explains what comes back (step-by-step screens/buttons/fields) and what to do next with the browser tools. The only gap is not naming which sibling returns actual feed data instead.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond the empty schema; baseline 4 applies. The description correctly implies no arguments are needed.

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

Purpose3/5

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

The description does state the resource (the user's Google Discover feed) and clarifies that the tool returns step-by-step instructions rather than the feed itself, which resolves the ambiguity in the name 'read feed'. However, it never distinguishes itself from plausible siblings like get_discover_feed or collect_discover_cards, so an agent cannot tell from this text which one actually returns cards versus instructions.

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?

It gives one useful routing hint: use this first, then execute the steps with cotlet_browser_* tools in the user's Google Discover Cloud Browser. There is no explicit when-not guidance and no statement about which sibling to pick when an agent just wants the cards, so usage is implied rather than prescribed.

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

All Google Discover 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