Skip to main content
Glama
ScrapeAdLibrary

ScrapeAdLibrary

Official

get_page

Retrieve an advertiser's profile details—name, category, likes, Instagram account and followers, verification status, and estimated current ad count—using a numeric page ID from search results.

Instructions

Get an advertiser's profile: name, category, likes, Instagram account and followers, verification, and an estimate of how many ads it is running now.

Cost: 1 credit.

Args: page_id: Numeric advertiser page ID (from search_ads results or search_pages).

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": {
      "page_id": "<page_id>"
    },
    "name": "get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the burden, and it does disclose two things structured fields do not: the credit cost and the exact profile fields returned. It says nothing about permissions, freshness of the ad-count estimate, or behavior on an invalid/unknown page_id.

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?

Front-loaded with the outcome, then cost, then the args block. Every line carries information the agent cannot get from the schema, with no filler.

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 single-parameter read tool with an output schema, this covers purpose, cost, and parameter provenance adequately. The remaining gap is failure behavior (unknown ID, rate limiting) which matters slightly less because the output schema defines the return shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% (the only param is just titled 'Page Id' as a string), so the description has to compensate, and it does: it reveals the ID is numeric despite the string type and tells the agent where to obtain it. It could additionally note the expected ID format or that the ID is not the page name.

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?

The description gives a specific verb ('Get') and resource ('an advertiser's profile') and even enumerates the returned fields (name, category, likes, Instagram followers, verification, active-ad estimate). That is enough to distinguish it from get_ad and get_page_ads in substance, but it never names those siblings to make the contrast explicit.

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?

It states where the required page_id comes from ('from search_ads results or search_pages') and discloses the 1-credit cost, which is real usage context rather than prose. It stops short of explicit when-not conditions or naming an alternative tool to use for other needs.

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