Skip to main content
Glama
mikusnuz

meta-ads-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_budget_schedules

Retrieve paginated budget schedules for a campaign or ad set to review and manage advertising budget allocations.

Instructions

List budget schedules attached to a campaign or ad set. Returns paginated results.

Input Schema

NameRequiredDescriptionDefault
afterNoPagination cursor for next page
limitNoNumber of results (default 25)
fieldsNoComma-separated fields to return
parent_idYesCampaign or ad set ID that owns the budget schedules
parent_typeNoType of parent objectcampaign

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.6.1
    • addedInput schema / properties / limit / exclusiveMinimum
      Added value: +0
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / parent_id
      Added value: +{
+  "description": "Campaign or ad set ID that owns the budget schedules",
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / parent_type
      Added value: +{
+  "default": "campaign",
+  "description": "Type of parent object",
+  "enum": [
+    "campaign",
+    "adset"
+  ],
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "parent_id"
+]
  2. First observedv1.2.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose one useful trait: results are paginated. However it says nothing about permission requirements, rate limits, whether parent_type must match the parent_id, or what a page contains, so it only partially covers the load.

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?

Two short, front-loaded sentences with zero filler; the scoping statement comes first and the pagination note second. Every sentence earns its place.

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 fully documented read-only list tool with one required parameter and no output schema, the definition covers purpose and the paginated-return behavior. It is slightly thin on operational context (no mention of how to page forward or what fields default to), but nothing critical to a correct call is missing.

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 100%, so pagination cursor, limit, fields, parent_id and the parent_type enum are all documented in the schema. The description adds no parameter meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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 specific verb and resource ('List budget schedules') plus the scoping object ('attached to a campaign or ad set'), so an agent immediately knows what is returned. It does not explicitly distinguish itself from create_budget_schedule/update_budget_schedule, but the read verb makes the distinction obvious without opening a schema.

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?

The description gives no when-to-use guidance, no prerequisite explanation, and names no alternative tool. 'Attached to a campaign or ad set' implies the required parent but the agent must infer that from the name and schema rather than being told.

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