Skip to main content
Glama

Facts and links for a post or ad

get_marketing_kit
Read-onlyIdempotent

Everything needed to write social posts, ads or an email about one of your listings: title, description, price, image links, the page link with tracking for the channel, and audience notes. Also returns a guide for the chosen channel (image shapes and sizes, how a post is usually built, where the link goes), what the listing photos should cover, and what copy must never claim. Write the copy from these facts only; never promise delivery times or quality guarantees. Needs a connected Printlooper account.

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": {
      "listing_id": "<listing_id>"
    },
    "name": "get_marketing_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNoinstagram
listing_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds genuinely new behavioral context: the response is channel-dependent (different image shapes, post structure, link placement), it includes compliance-style copy prohibitions, and it requires an authenticated account. It does not discuss failure modes for an invalid listing_id or channel, 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 what the caller gets, then what else is included, then the usage constraint and prerequisite. Every clause carries information, though the long comma-separated return list is dense and could be tightened without loss.

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, so the description must describe the return payload, and it does so in detail, including the channel-specific guide and the copy restrictions. The account prerequisite and the 'facts only' rule cover the main operational risks. The only real gap is guidance on listing_id validity/format, which the schema leaves undocumented.

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 0%, so the description must carry parameter meaning. It does well for 'channel', explaining that the chosen channel determines the returned guide and the tracking link on the page URL, which gives the 8-value enum real consequence. 'listing_id' is only implied by 'about one of your listings' with no format, ownership, or validation detail, so coverage is partial.

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 concrete verb and resource set: it returns title, description, price, image links, a tracked page link, audience notes, a per-channel guide, photo coverage guidance, and copy restrictions for a listing. That is far more specific than the title 'Facts and links for a post or ad' and clearly separates it from listing/design/product siblings that return raw data rather than marketing material.

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?

Usage context is explicit: use it when writing social posts, ads, or an email about a listing, and it states the hard constraint 'Write the copy from these facts only; never promise delivery times or quality guarantees.' It also names a prerequisite ('Needs a connected Printlooper account'). It stops short of naming alternatives or when NOT to use it, so it lands at 4 rather than 5.

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.

Resources