Skip to main content
Glama

Create Custom Conversion

meta_create_custom_conversion

Create a custom conversion to track specific user actions on your website by defining a URL rule, associating it with a pixel, and selecting an event type.

Instructions

Creates a custom conversion for tracking specific actions.

Args:

  • ad_account_id (string): Ad account ID

  • name (string): Conversion name

  • pixel_id (string): Pixel ID to associate with

  • custom_event_type (string): Event type — CONTENT_VIEW, SEARCH, ADD_TO_CART, ADD_TO_WISHLIST, INITIATED_CHECKOUT, ADD_PAYMENT_INFO, PURCHASE, LEAD, COMPLETE_REGISTRATION, OTHER

  • rule (string): URL rule as JSON (e.g., {"url":{"i_contains":"thank-you"}})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ad_account_idYes
nameYes
pixel_idYes
custom_event_typeYes
ruleYesURL rule as JSON string
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior2/5

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

Annotations provide no hints (all false), and description only says 'Creates' but does not disclose if it overwrites existing conversions, permission requirements, rate limits, or that it is a write operation beyond creation.

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?

Short paragraph plus list, no fluff, front-loaded purpose. Could be slightly more structured for parameter descriptions but overall efficient.

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?

Adequately describes creation and parameters, but lacks mention of return value (no output schema), prerequisites (e.g., existing pixel), or error conditions. Example for rule is helpful.

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?

Description adds some value beyond schema: lists enum values for custom_event_type, provides example for rule. However, it does not explain the meaning of ad_account_id or pixel_id. Schema has 33% description coverage, so description partially compensates.

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?

Clearly states verb+resource: 'Creates a custom conversion for tracking specific actions.' Distinguishes from sibling tools like 'meta_list_custom_conversions'.

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?

No guidance on when to use this tool vs alternatives or prerequisites. Does not mention that a pixel must exist first or that a custom conversion is used for ad tracking.

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/oliverames/meta-mcp-server'

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