Skip to main content
Glama
Sign In

Apogee: Bulk Ad Launcher for Meta, TikTok & Snapchat

by ad.apogee
OverviewDiscussionsAdmin

Summarize the brand's website

fetch_website_content
Read-onlyIdempotent

Summarize the brand's website (voice, products, claims) to write ads. Fetch and summarize the user's brand website to extract brand voice, product positioning, target persona, and key claims. Call this when you need product context for a creative strategy prompt and website_url is known in the business profile. Cache 7 days — if cached, reuses the stored summary unless the user asks to refresh.

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": {
      "url": "<url>"
    },
    "name": "fetch_website_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull URL (https://...). Use website_url from the business profile unless the user gives another.
ad_account_idNoMeta ad account id (act_…), from list_ad_accounts
force_refreshNoSet true to bypass cache and re-crawl

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: a 7-day cache that reuses the stored summary unless the user asks to refresh. It does not cover failure modes (unreachable or JS-heavy sites) or crawl latency, which keeps it below 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?

Three sentences, front-loaded with the purpose then the trigger then the cache caveat, with no filler. There is minor redundancy between the title-like opening phrase and the second sentence's 'Fetch and summarize the user's brand website', but nothing that impairs scanning.

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?

There is no output schema, and the description compensates by naming the four extracted artifacts the caller receives. Combined with the cache note and the URL-sourcing hint, an agent has enough to invoke correctly; only error handling for uncrawlable URLs is unaddressed.

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 all three parameters are already documented, giving a baseline of 3. The description reinforces force_refresh by explaining the 7-day cache window it bypasses, but adds no syntax, format, or validation detail beyond what the schema supplies.

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 ('Fetch and summarize the user's brand website') plus the exact extraction targets: brand voice, product positioning, target persona, key claims. This is clearly distinguishable from data-listing siblings like get_business_profile or fetch_customer_reviews, though no sibling is named explicitly.

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?

Gives a concrete trigger condition: 'Call this when you need product context for a creative strategy prompt and website_url is known in the business profile.' That is a clear when-to-use with a precondition. It lacks explicit when-not guidance (e.g., when the site is already summarized in a prior turn or when the user supplies no URL), so it falls short of a 5.

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