Skip to main content
Glama
Sign In

Google Discover MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Check domain in feed in Google Discover

google_discover_check_domain_in_feed
Read-onlyIdempotent

Check domain in 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_check_domain_in_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish that this is read-only, closed-world, idempotent, and non-destructive. The description adds useful behavioral context beyond them: it opens nothing by itself, returns screen/button/field instructions, and explains that Google Discover has no feed API. It does not discuss authentication or user-account prerequisites for the subsequent browser workflow.

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?

The action is front-loaded, and the second sentence promptly clarifies that the tool only returns instructions. The API note supports the browser handoff, but the phrase 'from ChatGPT, Claude or any AI agent' and the dated API parenthetical are somewhat expendable.

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?

Because there is no output schema, the description needs to explain the return content, and it does: step-by-step screens, buttons, and fields. It also explains the no-side-effect behavior and the next tools to use, though it could be clearer about how the domain and account context are provided to the downstream browser flow.

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?

This is a zero-parameter tool, so there are no parameter semantics to explain, and the schema is fully described. The description does not invent parameters or misrepresent inputs, though it could clarify that the specific domain is supplied later in the browser workflow.

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 identifies a specific action and resource: checking a domain in the user's own Google Discover feed. It also clarifies that the tool returns step-by-step instructions rather than performing the check itself. It does not, however, distinguish this tool from the similarly named sibling check_domain_in_feed or the feed-reading 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 a clear intended workflow: get the step-by-step instructions here, then execute them with cotlet_browser_* tools in the Google Discover Cloud Browser. It does not state when not to use this tool or why an agent should choose it over sibling check_domain_in_feed or the feed-reading alternatives.

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