Skip to main content
Glama
x51xxx

OSP Marketing Tools MCP Server

by x51xxx

get_meta_guide

Generate optimized meta titles, descriptions, and slugs for web content with keyword placement and search intent analysis.

Instructions

Get the Open Strategy Partners (OSP) Web Content Meta Information Generation System for creating optimized article titles, meta titles, meta descriptions, and slugs for web content with proper keyword placement and search intent analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The complete tool handler implementation for 'get_meta_guide', registered inline. It reads the 'meta-llm.md' file using the injected contentReader utility and returns its content as structured JSON response, handling errors appropriately.
    server.tool(
      "get_meta_guide", 
      "Get the Open Strategy Partners (OSP) Web Content Meta Information Generation System for creating optimized article titles, meta titles, meta descriptions, and slugs for web content with proper keyword placement and search intent analysis.",
      async (_extra) => {
        try {
          const content = await contentReader.readMarkdownFile('meta-llm.md');
          return {
            content: [{
              type: "text",
              text: JSON.stringify({
                success: true,
                data: { content }
              })
            }]
          };
        } catch (error) {
          return {
            content: [{
              type: "text",
              text: JSON.stringify({
                success: false,
                error: error instanceof Error ? error.message : String(error)
              })
            }],
            isError: true
          };
        }
      }
    );
  • Registration of the 'get_meta_guide' tool via server.tool() within the registerTools function.
    server.tool(
      "get_meta_guide", 
      "Get the Open Strategy Partners (OSP) Web Content Meta Information Generation System for creating optimized article titles, meta titles, meta descriptions, and slugs for web content with proper keyword placement and search intent analysis.",
      async (_extra) => {
        try {
          const content = await contentReader.readMarkdownFile('meta-llm.md');
          return {
            content: [{
              type: "text",
              text: JSON.stringify({
                success: true,
                data: { content }
              })
            }]
          };
        } catch (error) {
          return {
            content: [{
              type: "text",
              text: JSON.stringify({
                success: false,
                error: error instanceof Error ? error.message : String(error)
              })
            }],
            isError: true
          };
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes what the system does (generates optimized content elements) but lacks details on behavioral traits such as whether this is a read-only operation, if it requires authentication, rate limits, or what the output format looks like. This is a significant gap for a tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single run-on sentence that packs multiple concepts (system name, purpose, elements generated, and analysis features). While it conveys key information, it could be more structured and front-loaded for clarity. It's not overly verbose but could be tightened for better readability.

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?

Given the complexity implied by generating optimized content with search intent analysis, and with no annotations or output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., a guide, template, or generated text), how to interpret results, or any operational constraints, leaving gaps for effective agent use.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, which is efficient. However, it could have mentioned if any implicit inputs or context are required, but this is minor, warranting a high score.

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

Purpose3/5

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

The description states the tool retrieves a specific system (OSP Web Content Meta Information Generation System) for creating optimized web content elements, which is a clear purpose. However, it doesn't distinguish this from sibling tools like 'get_on_page_seo_guide' or 'get_writing_guide' that might cover overlapping SEO/content optimization areas, making it somewhat vague about its unique scope.

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 implies usage for generating article titles, meta titles, descriptions, and slugs with keyword placement and search intent analysis, but provides no explicit guidance on when to use this tool versus alternatives like 'get_on_page_seo_guide' or 'get_writing_guide'. There are no exclusions or prerequisites mentioned, leaving usage context unclear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/x51xxx/osp-marketing-tools-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server