Skip to main content
Glama
Sign In
Meta Ads MCP

Meta Ads MCP

by AbnerZx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ads_get_adset_schedule

Retrieve an ad set's day-parting schedule and view it in human-readable format. Decodes Meta's raw schedule into Portuguese day names and HH:MM times, and indicates if the ad set runs 24/7 when no schedule is set.

Instructions

Read an ad set's day-parting schedule, decoded into human-readable form.

Returns both the raw adset_schedule (Meta format) and a decoded view with Portuguese day names and HH:MM times. Returns enabled: False when no day-parting block is set (ad set runs 24/7 inside its start/end window).

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": {
      "adset_id": "<adset_id>"
    },
    "name": "ads_get_adset_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
adset_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are provided, so the description is the sole source. It discloses the return format (raw + decoded), the behavior when no day-parting block exists (enabled: False), and implies read-only nature. This adds useful behavioral context beyond the schema.

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

Conciseness5/5

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

The description is three sentences, front-loaded with the purpose, then details. Every sentence adds value without redundancy.

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 simple read tool with one parameter and no output schema, the description covers the return values and an edge case. It lacks error handling details, but those are not essential for a straightforward read operation.

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?

The schema provides only a string type for adset_id with no description, and the description does not explain the parameter's meaning or usage. With 0% schema coverage, the description should compensate, but it doesn't address the parameter at all.

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

Purpose5/5

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

The verb 'Read' clearly specifies the action, and the resource 'ad set's day-parting schedule' is precise. It also distinguishes from the sibling 'ads_set_adset_schedule' by being the read counterpart and mentions decoding.

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?

The description implies usage for reading schedules, but does not explicitly state when to use it over alternatives or mention exclusions. The 'Read' verb makes it clear, but it lacks explicit guidance about when not to use.

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