Skip to main content
Glama
gingerlive-io

GingerLive MCP Server

Official
by gingerlive-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List case studies

list_case_studies
Read-onlyIdempotent

Find proof points and results for a brand, category, or ad format by listing case studies with slug, title, excerpt, and URL; then fetch the full write-up.

Instructions

Lists GingerLive campaign case studies with slug, title, short excerpt and URL. Use to find proof points or results for a brand, category or format, then call get_case_study with a slug for the full write-up. 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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'Read-only' in the description is redundant reinforcement. The description does usefully disclose the return shape, but says nothing about result volume, pagination, or filtering limits.

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?

Three short sentences, front-loaded with what it returns, then routing, then a one-word safety tag. No filler text.

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?

With no output schema, the description correctly compensates by naming the fields returned, and the next-step routing completes the picture. Minor gaps remain around list size or pagination, but nothing needed to invoke the tool 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 coverage is 100%, so the single 'intent' parameter is fully documented in the schema itself. The description adds no meaning about this parameter (e.g. that it is telemetry-only and never filters results), so 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 and resource ('Lists GingerLive campaign case studies') and enumerates the returned fields (slug, title, excerpt, URL). An agent can immediately distinguish it from get_case_study, which returns the full write-up.

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 ('to find proof points or results for a brand, category or format') and names the follow-up alternative with the condition that selects it ('then call get_case_study with a slug'). The routing chain is unambiguous.

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