Skip to main content
Glama

get_meta_guide

Generate optimized meta titles, descriptions, and slugs for web content using Open Strategy Partners' methodologies to improve SEO and content positioning.

Instructions

Get the Open Strategy Partners (OSP) Web Content Meta Information Generation System (titles, meta-titles, slugs).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'get_meta_guide' tool. It reads the content from 'meta-llm.md' file and returns it wrapped in a success dict, or error if file not found. Registered via @mcp.tool() decorator.
    @mcp.tool()
    async def get_meta_guide() -> dict:
        """Get the Open Strategy Partners (OSP) Web Content Meta Information Generation System (titles, meta-titles, slugs)."""
        script_dir = os.path.dirname(os.path.abspath(__file__))
        try:
            with open(os.path.join(script_dir, 'meta-llm.md'), 'r') as f:
                content = f.read()
                return {
                    "success": True,
                    "data": {
                        "content": content
                    }
                }
        except FileNotFoundError:
            return {
                "success": False,
                "error": "Required file 'meta-llm.md' not found in script directory"
            }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states what the tool retrieves but doesn't disclose behavioral traits such as whether it's a read-only operation, potential rate limits, authentication needs, or what the output format might be. For a tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a no-parameter tool, though it could be slightly more structured by front-loading key details like the verb 'retrieve' more explicitly.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., a list, a single object, or structured data), any behavioral constraints, or how it differs from sibling tools. For a tool with no structured metadata, the description should provide more context to aid the agent.

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, meaning no parameters are documented in the schema. The description doesn't add parameter details, which is appropriate since there are no parameters. This aligns with the baseline expectation for tools without parameters, as there's nothing to compensate for.

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 'Web Content Meta Information Generation System' data including titles, meta-titles, and slugs, which is a clear purpose. However, it doesn't specify what 'get' means operationally (e.g., fetch all, fetch by ID, search) or differentiate from sibling tools like 'get_on_page_seo_guide' that might overlap in scope. The description is somewhat vague about the exact nature of the retrieval.

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 on when to use this tool versus alternatives. The description doesn't mention sibling tools, prerequisites, or specific contexts for usage. It's left to the agent to infer based on the tool name and description alone, which is insufficient for optimal tool selection.

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/open-strategy-partners/osp_marketing_tools'

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