Skip to main content
Glama

ADS Beast

recommendation_list

Read-only

Open recommendation cards: agent advice and Meta's own cabinet advice, judged against the client's goal.

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

Input Schema

NameRequiredDescriptionDefault
limitNo10 by default, 30 at most.
sourceNometa_native for Meta's cabinet advice.
platformNogoogle, meta, tiktok, linkedin or microsoft.
client_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare read-only, open-world, and non-destructive behavior, so the safety profile is clear. The description adds useful scope by naming the two recommendation sources and the client-goal framing, but it does not describe return structure, pagination behavior, or whether recommendations are unresolved versus merely unsaved.

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 definition is a single front-loaded sentence with no redundant filler. The phrase 'judged against the client's goal' is slightly vague, but the description remains compact and readable.

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 read-only list tool with no output schema, the description covers the core resource and source scope but leaves important operational details implicit. It does not clarify what 'open' means precisely, how results are ordered or paginated, or how the optional client_id affects the judgment criteria.

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?

Schema description coverage is 75%, so parameter documentation largely comes from the schema. The description reinforces the source distinction through 'Meta's own cabinet advice' but does not explain the limit, platform values, or the client_id parameter beyond a vague reference to the client's goal.

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 the resource as open recommendation cards, with two distinct sources: agent advice and Meta's cabinet advice, judged against the client's goal. This is more specific than the title alone, though it does not explicitly contrast itself with recommendation_save or other recommendation-related tools.

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?

There is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternative such as recommendation_save. The word 'Open' implies retrieval of unresolved recommendations, but the agent is left to infer that condition.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.