Skip to main content
Glama
x51xxx

OSP Marketing Tools MCP Server

by x51xxx

get_on_page_seo_guide

Access the OSP On-Page SEO Optimization Guide to optimize web content with meta tags, keyword research, content depth, search intent alignment, internal linking, and structured data.

Instructions

Get the Open Strategy Partners (OSP) On-Page SEO Optimization Guide for comprehensive web content optimization, covering meta content, keyword research, content depth, search intent alignment, internal linking, and structured data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that reads the 'on-page-seo-guide.md' file using ContentReader, returns its content in MCP format on success, or an error response on failure.
    async (_extra) => {
      try {
        const content = await contentReader.readMarkdownFile('on-page-seo-guide.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
        };
      }
    }
  • Registers the 'get_on_page_seo_guide' tool with the MCP server inside the registerTools function.
    server.tool(
      "get_on_page_seo_guide", 
      "Get the Open Strategy Partners (OSP) On-Page SEO Optimization Guide for comprehensive web content optimization, covering meta content, keyword research, content depth, search intent alignment, internal linking, and structured data.",
      async (_extra) => {
        try {
          const content = await contentReader.readMarkdownFile('on-page-seo-guide.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
          };
        }
      }
    );
  • Supporting method in ContentReader class to asynchronously read and cache markdown files, used by the tool handler to load the SEO guide content.
    async readMarkdownFile(filename: string): Promise<string> {
      // Check cache
      if (this.cache.has(filename)) {
        return this.cache.get(filename)!;
      }
    
      try {
        const filePath = join(this.resourcesDir, filename);
        const content = await readFile(filePath, 'utf-8');
        
        // Store in cache
        this.cache.set(filename, content);
        
        return content;
      } catch (error) {
        console.error(`Error reading file ${filename}:`, error);
        throw new Error(`Required file '${filename}' not found`);
      }
    }
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 states this is a 'Get' operation which implies read-only behavior, but doesn't explicitly confirm this or mention any other behavioral traits like authentication requirements, rate limits, response format, or potential side effects. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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, well-structured sentence that efficiently conveys the tool's purpose and scope. It front-loads the core function ('Get the Open Strategy Partners (OSP) On-Page SEO Optimization Guide') and then provides useful detail about what the guide covers. Every part of the sentence adds value without redundancy.

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

Completeness3/5

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

For a zero-parameter tool with no output schema and no annotations, the description provides adequate but minimal information. It tells what resource is retrieved and what topics it covers, but doesn't describe the return format, potential errors, or any operational constraints. Given the simplicity of the tool (no parameters), the description meets minimum viable standards but could be more complete regarding behavioral expectations.

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 has zero parameters (input schema is empty object), so there are no parameters to document. The description appropriately doesn't discuss parameters since none exist. With 100% schema description coverage and zero parameters, a baseline of 4 is appropriate as the description doesn't need to compensate for any parameter documentation gaps.

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 tool's purpose: 'Get the Open Strategy Partners (OSP) On-Page SEO Optimization Guide' with specific details about what the guide covers (meta content, keyword research, etc.). It uses a specific verb ('Get') and identifies the resource (OSP guide). However, it doesn't explicitly differentiate from sibling tools like 'get_meta_guide' or 'get_writing_guide' beyond mentioning SEO focus.

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. It doesn't mention when this SEO guide would be preferred over the 'get_meta_guide' or 'get_writing_guide' siblings, nor does it specify any prerequisites or contextual triggers for its use. The description simply states what the tool provides without usage context.

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