Skip to main content
Glama
Sign In

Apogee: Bulk Ad Launcher for Meta, TikTok & Snapchat

by ad.apogee
OverviewDiscussionsAdmin

Brand profile

get_business_profile
Read-onlyIdempotent

The brand's saved profile for an ad account: site, margins, CPA and ROAS targets. Read the stored business profile for the current ad account. Returns known fields (website_url, brand_name, category, business_type, target_cac, target_roas, target_mer, product_margin_pct, ltv, repeat_purchase_rate_pct, primary_objective, etc.) plus the list of fields still missing. USE THIS FIRST when a prompt requires business context (e.g. scaling decisions, customer review analysis). If required fields are missing, ASK the user for them in plain language, then call update_business_profile to persist.

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": {
      "ad_account_id": "<ad_account_id>"
    },
    "name": "get_business_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
ad_account_idYesMeta ad account id (act_…), from list_ad_accounts

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds real value beyond them by enumerating the returned fields and disclosing that the response includes 'the list of fields still missing' — a behavioral trait an agent must know to decide whether to prompt the user. It stops short of describing failure modes (e.g., no profile saved yet, or an account with zero populated fields), which keeps it off a 5.

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?

Front-loads the resource and contents, then the imperative 'USE THIS FIRST', then the missing-field workflow — good ordering with no filler sentences. The first sentence ('The brand's saved profile for an ad account: site, margins, CPA and ROAS targets') partially restates the second ('Read the stored business profile...'), so there is a small amount of duplication.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by listing the known return fields and the missing-fields list, so an agent knows what comes back. For a one-parameter read tool with full annotation coverage, nothing needed to call it correctly or interpret the result is absent.

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?

There is one parameter and schema coverage is 100%, so the schema already documents ad_account_id, its pattern, and its provenance from list_ad_accounts. The description adds no format or sourcing detail beyond that, so the baseline 3 for schema-carried parameters applies.

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?

States a specific verb and resource ('Read the stored business profile for the current ad account') and scopes it to a single ad account. The first line names the concrete contents (site, margins, CPA and ROAS targets), which distinguishes it from every sibling in the list, none of which read a stored profile.

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

Usage Guidelines5/5

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

Explicitly instructs 'USE THIS FIRST when a prompt requires business context (e.g. scaling decisions, customer review analysis)' and names the follow-up path: ask the user in plain language, then call update_business_profile. This is a stated when-to-use, a concrete trigger condition, and a named alternative destination for the write step.

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

All Apogee: Bulk Ad Launcher for Meta, TikTok & Snapchat toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources