Skip to main content
Glama
gingerlive-io

GingerLive MCP Server

Official
by gingerlive-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Company overview

get_company_overview
Read-onlyIdempotent

Answer what GingerLive is by retrieving its company profile, supported livestream platforms, network stats, measurement partners, and contact links.

Instructions

Returns GingerLive's company profile: what the livestream advertising platform does, supported streaming platforms (Twitch, Kick, YouTube Live, TikTok LIVE), headline network stats, third-party measurement partners and contact links. Use first for general "what is GingerLive" questions; use get_network_stats for just the reach numbers, list_ad_formats for formats, get_streamer_program_info for the creator side. Read-only; data is a static snapshot of gingerlive.io's public facts.

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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety and determinism profile is covered. The description adds genuinely new context beyond that: the data is a 'static snapshot of gingerlive.io's public facts', telling the agent results are cached/public and not live. It stops short of noting response verbosity or shape, but with annotations carrying the safety burden this is solid.

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 routing guidance, then a behavioral footnote. Every clause is functional, though the parenthetical platform list and partner/contact enumeration make it denser than strictly necessary for selection.

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?

There is no output schema, and the description compensates by enumerating what the response contains (profile, platforms, stats, partners, links) plus its static/public nature. Nothing an agent needs to call this correctly is missing.

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% and there is a single optional 'intent' parameter fully documented in the schema, including what not to include (personal data). The description adds nothing about the parameter, so the baseline of 3 applies — the schema does all the work here.

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 (Returns) and resource (GingerLive's company profile) and enumerates the concrete contents: platform description, supported streaming platforms, network stats, measurement partners, contact links. It explicitly names the siblings it is not (get_network_stats, list_ad_formats, get_streamer_program_info), so an agent can distinguish it without opening any schema.

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?

Gives an explicit trigger condition ('Use first for general "what is GingerLive" questions') and pairs each alternative use case with its dedicated sibling tool. Nothing about when to pick this over the others is left to inference.

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