Skip to main content
Glama

growthintel-mcp

Creative Strategy Recommendations Tool

creative-strategy-recommendations-tool
Read-onlyIdempotent

Returns AI-generated creative strategy guidance for the authenticated tenant's paid ads: which audience segments (profession, role, city) convert best against existing creatives, and which high-volume-low-quality segments should move to awareness-only spend. This evaluates existing creative+audience performance — it does not draft new ad copy. Needs enough lead volume to be meaningful; returns available=false with a reason (e.g. insufficient_data) when it can't.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "creative-strategy-recommendations-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered; the description adds genuinely new behavior — tenant scoping via the authenticated tenant and a documented degraded response shape ("available=false with a reason (e.g. insufficient_data)"). That failure-mode disclosure is the main thing an agent needs to handle the call, though it doesn't say what the successful payload looks like.

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 tight sentences with zero filler: purpose and returned insight first, then the non-goal, then the precondition and degraded response. Front-loaded and every sentence carries distinct information.

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?

For a zero-parameter, read-only, no-output-schema tool, the description covers what is returned (segment-level strategy recommendations), what is out of scope (ad copy drafting), and the failure case (insufficient data). Nothing an agent needs in order to decide to call it or interpret a failure is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to explain and nothing in the schema for the description to compensate for. Baseline 4 applies; the description correctly implies the call is fully scoped by the authenticated tenant rather than by arguments.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (AI-generated creative strategy guidance for paid ads) and spells out the exact questions answered: which profession/role/city segments convert best, and which high-volume-low-quality segments should shift to awareness-only spend. It also draws a functional boundary ("does not draft new ad copy"), which helps separate it from copy-generation tools, though the phrase "evaluates existing creative+audience performance" partially blurs the line with the sibling creative-performance-tool.

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 states the precondition for meaningful use ("needs enough lead volume") and scopes the tool to optimization/strategy decisions about existing creatives and audiences. It does not explicitly name what to call instead when the goal is raw performance numbers or new copy, leaving that routing to inference.

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