Skip to main content
Glama
Sign In
reddit-ads-mcp

reddit-ads-mcp

by filippofinke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get product set

reddit_ads_get_product_set
Read-only

Retrieve a Reddit Ads product set by ID to inspect its catalog configuration and use it for campaign targeting.

Instructions

Get a product set.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product_set_id": "<product_set_id>"
    },
    "name": "reddit_ads_get_product_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_set_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, so the safety profile is already covered. The description adds nothing on top of that — no note about scoping, permissions, or what a retrieved product set represents, so it contributes essentially zero behavioral context.

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

Conciseness2/5

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

The single sentence is terse and front-loaded, but it is under-specified rather than concise — it wastes its one sentence restating the name instead of conveying anything useful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only lookup tool with no output schema and one undocumented parameter, the description should at minimum explain what a product set is and how the ID is obtained. Neither is present, so it is incomplete for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the schema only supplies a required string named product_set_id with no format or provenance. The description says nothing about the parameter, leaving the agent without guidance on where the ID comes from or how it should look.

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

Purpose2/5

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

The description 'Get a product set.' merely restates the tool name and title, adding no information beyond the verb+resource already implied. It does not distinguish this retrieval tool from siblings like reddit_ads_list_product_sets or reddit_ads_list_product_set_products.

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 guidance on when to use this tool, what prerequisite steps are needed to obtain a valid product_set_id, or how it relates to the sibling list/create/update/delete product set tools. Usage must be inferred entirely from the name.

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

Deploy Server

Other Tools