Skip to main content
Glama

Ad Spec Guard

get_platform_specs

Read-only

Return the verified specification sheet for one ad platform: hard character limits per copy field, image formats with their required dimensions and file size caps, learning-phase windows, and the conversion history automated bidding needs. Call this before writing ad copy or briefing creative, instead of relying on remembered limits, which change and are frequently misremembered.

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": {
      "platform": "<platform>"
    },
    "name": "get_platform_specs"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionNoWhich part of the sheet to return.all
platformYesAd platform. One of: google, linkedin, meta, microsoft, telegram, tiktok.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already establish readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds useful behavioral context by framing the data as 'verified' and noting that limits change frequently, though it does not describe caching, error behavior, or return structure.

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?

Two sentences, front-loaded with the core purpose and followed by a clear usage instruction. Every clause contributes specific information with no filler.

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?

This is a low-complexity read-only lookup with no output schema. The description lists what the sheet contains and when to call it, which is sufficient for an agent to invoke it correctly without needing return-shape details.

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 the platform and section parameters are already documented with enums and meanings. The description adds thematic mapping to the sheet contents but no additional parameter syntax, defaults, or edge-case semantics 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 names a specific verb and resource: 'Return the verified specification sheet for one ad platform.' It enumerates the exact contents (character limits, image dimensions, learning-phase windows, conversion history), making clear this is a reference lookup rather than a validator or policy check.

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 gives a clear timing instruction: call before writing ad copy or briefing creative, and explains why (remembered limits change and are misremembered). It does not explicitly name sibling tools such as validate_ad_copy as alternatives, but the usage context is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.