Skip to main content
Glama
gingerlive-io

GingerLive MCP Server

Official
by gingerlive-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Ad formats

list_ad_formats
Read-onlyIdempotent

Lists livestream ad formats sold by GingerLive, including badges like unskippable and adblock-safe, to help brands compare and plan campaigns.

Instructions

Lists the livestream ad formats GingerLive sells to brands (e.g. picture-in-picture, banners, rich media, pinned chat drops, streamer announcements), each with a short description, plus format badges such as unskippable and adblock-safe. Use when planning or comparing ad formats; use get_company_overview for the company itself. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
intentNoOptional: one short sentence on what the user is trying to accomplish, e.g. 'compare ad formats for a gaming product launch in Turkey'. Used only to improve this server's coverage. Do not include names, emails or other personal data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / intent
      Added value: +{
+  "description": "Optional: one short sentence on what the user is trying to accomplish, e.g. 'compare ad formats for a gaming product launch in Turkey'. Used only to improve this server's coverage. Do not include names, emails or other personal data.",
+  "maxLength": 300,
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered and the trailing 'Read-only' is largely redundant. The description does add value by disclosing what the response contains (a short description per format plus badges like unskippable and adblock-safe), though it says nothing about result size, pagination, or caching.

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-loaded with the resource and its contents, then the routing rule; three sentences with no filler. The parenthetical example list is somewhat long but earns its place by making the formats concrete for comparison tasks.

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 zero-required-param list tool with no output schema, the description covers purpose, contents, usage, and the sibling alternative, which is close to sufficient. The only gap is that the single optional 'intent' parameter and any auth/prerequisite context go unmentioned.

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?

One optional parameter with 100% schema description coverage, so the schema already explains the 'intent' hint fully. The description never mentions the parameter or that it is optional telemetry-only, so it adds nothing beyond the structured field; baseline 3 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 (lists) and resource (livestream ad formats GingerLive sells), and enumerates concrete examples (picture-in-picture, banners, pinned chat drops) so an agent knows exactly what domain this covers. It also names what each item carries (short description, badges), distinguishing it from the sibling overview tools.

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 says when to use it ('planning or comparing ad formats') and routes the agent to the correct alternative ('use get_company_overview for the company itself'), which is the key ambiguity given the sibling set of company/case-study tools.

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