Skip to main content
Glama
Sign In
Launch Engine

Launch Engine

by ZionHopkins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

content_engine

Read-only

Research topic clusters, generate pillar and spoke content, add schema markup, and establish AI visibility baselines to improve organic search and GEO performance.

Instructions

Organic Content & SEO/GEO Engine — topic cluster research, pillar/spoke content generation, schema markup, AI visibility baselines.

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": {
      "market_name": "<market_name>"
    },
    "name": "content_engine"
  }
}

Input Schema

NameRequiredDescriptionDefault
market_nameYesThe market/pipeline slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3/5.0
Behavior1/5

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

Annotations indicate readOnlyHint=true, but the description mentions 'content generation', implying write operations, contradicting the annotation. No additional behavioral details (auth, rate limits, etc.) are provided.

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?

One concise sentence front-loads the core purpose ('Engine') and lists activities. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with multiple capabilities and no output schema, the description is too brief. It fails to explain return values, behavior under different inputs, or how the engine produces results.

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% with a single parameter 'market_name' well-documented as 'The market/pipeline slug'. The description adds no additional parameter meaning, 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?

The description clearly states the tool is an 'Organic Content & SEO/GEO Engine' and lists specific activities (topic cluster research, pillar/spoke content generation, schema markup, AI visibility baselines), distinguishing it from siblings like seo_check or traffic_analytics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, such as whether to use it for content creation vs. diagnostic tools like seo_check.

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