Skip to main content
Glama
hashcott

Meta Ads MCP Server

by hashcott

Get Meta Campaign by ID

meta_ads_get_campaign_by_id
Read-onlyIdempotent

Retrieve detailed information about a specific Meta ad campaign by providing its campaign ID. Get fields like objective, status, budget, and more.

Instructions

Retrieve detailed information about a specific Meta ad campaign.

Args:

  • campaign_id (string): Campaign ID, e.g., '23843xxxxx'

  • fields (string[]): Fields to retrieve. Available: id, name, account_id, objective, status, effective_status, configured_status, daily_budget, lifetime_budget, budget_remaining, spend_cap, bid_strategy, buying_type, created_time, updated_time, start_time, stop_time, special_ad_categories, pacing_type, promoted_object, issues_info, recommendations

  • date_format (string): Date format: 'U' for Unix timestamp, 'Y-m-d H:i:s' for MySQL datetime, default: ISO 8601

Returns: Object with the requested campaign fields.

Examples:

  • Use when: "Get details for campaign 23843xxxxx"

  • Use when: "What is the objective and status of my campaign?"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYesCampaign ID, e.g., '23843xxxxx'
fieldsNoList of specific fields to retrieve. If omitted, default fields are returned
date_formatNoFormat for date fields in response. 'U' = Unix timestamp (seconds), 'Y-m-d H:i:s' = MySQL datetime. Default: ISO 8601
Behavior3/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, which the description respects. The description adds context by listing available fields and describing return format, but does not go beyond what annotations already indicate about safety.

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 description is well-structured with clear sections (summary, Args, Returns, Examples) and front-loaded purpose. Every sentence adds value, though slightly verbose with redundant examples.

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?

Despite no output schema, the description explains the return format and lists available fields and date format options. It covers sufficient detail for a simple retrieval tool, leaving little ambiguity.

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 coverage is 100%, so the description's parameter details largely duplicate the schema. It adds minor value by listing example values and default date format, but does not compensate significantly beyond the schema.

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 description clearly states 'Retrieve detailed information about a specific Meta ad campaign,' specifying the verb and resource. It includes examples and distinguishes itself from siblings that retrieve campaigns by other criteria.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides 'Use when' examples, indicating clear usage context. However, it does not explicitly mention when not to use or suggest alternatives among the many sibling tools, though the sibling list implies differentiation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hashcott/meta-ads-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server