Skip to main content
Glama
Sign In
Marketic

Marketic

by Das-rebel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

generate_seo_content

Create SEO-optimized content: meta titles, descriptions, headers, and FAQs tailored to your target keyword. Produce structured, keyword-focused copy that answers search intent.

Instructions

Generate SEO-optimized content including meta titles, descriptions, headers, and FAQs for target keywords.

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": {
      "target_keyword": "<target_keyword>"
    },
    "name": "generate_seo_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
word_countNo
content_typeNoblog_post
competitor_urlNo
target_keywordYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations provided, the description is the sole source of behavioral info. It only states that content is generated, but discloses no side effects, prerequisites, return format, or operational constraints. This is a minimal disclosure for a generation tool.

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?

The description is a single, front-loaded sentence with no waste. It packs the core action and key deliverables efficiently, though it omits necessary detail elsewhere.

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

Completeness1/5

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

For a tool with 4 parameters, no output schema, and no annotations, the description is severely under-specified. It does not clarify the output format, how parameters affect results, or any limitations. An agent would have to guess about response shape and behavior.

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

Parameters1/5

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

The schema has 0% description coverage, yet the description does not elaborate on any parameter except a vague mention of 'target keywords', which maps to the required parameter. word_count, content_type, and competitor_url are entirely unexplained, forcing the agent to rely on raw schema types and defaults.

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 clearly states the verb 'generate' and the resource 'SEO-optimized content', listing specific outputs (meta titles, descriptions, headers, FAQs). It implies distinction from siblings like generate_social_posts or generate_creatives, but does not explicitly differentiate.

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?

No guidance is provided about when to use this tool versus other content-generation or analysis tools among the many siblings. There is no explicit context, alternatives, or exclusions, leaving the agent to infer from the name.

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