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

reddit-ads-mcp

by filippofinke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List time zones

reddit_ads_list_time_zones
Read-only

Fetch all supported time zones for Reddit Ads to schedule campaigns and target audiences correctly. Supports pagination for large lists.

Instructions

List supported time zones.

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

Input Schema

NameRequiredDescriptionDefault
max_pagesNoFollow pagination.next_url up to this many pages and merge results (default 1)
page_sizeNoItems per page (usually max 1000)
page_tokenNoPage token from a previous pagination.next_url

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds nothing further – no note that this is a static/enumerable reference set, no pagination behavior, no indication of result size or ordering.

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?

A single front-loaded sentence with no wasted words. It is arguably too terse for its job, but as a conciseness measure it is efficient and well-structured.

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 simple read-only reference-list tool with a fully described schema and no output schema, a one-line description is close to sufficient. It stops short of telling the agent what the returned time-zone identifiers look like or where they should be applied, which is the only remaining gap.

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?

The schema documents all three pagination parameters at 100% coverage, so the baseline of 3 applies. The description adds no parameter-level detail (no hint about page_size limits or default merge behavior) beyond what the schema already carries.

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?

States a clear verb+resource ('List supported time zones'), so the agent knows it returns a reference list of valid time-zone values. It isn't differentiated from similar lookup siblings such as list_languages, list_devices or list_industries, but the resource is unambiguous.

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 call this versus other enumeration tools, nor any note that the returned values are meant to feed other calls (e.g. campaign scheduling). The agent must infer the use case entirely.

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