Skip to main content
Glama

generate_etsy_seo

Generate SEO-optimized Etsy product titles, descriptions, and tags to help your listings rank higher in search results and attract more customers.

Instructions

Generate SEO-optimized Etsy product title, description, and tags. Free: 10 generations/month.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoOptional product category (e.g., "Home & Living")
product_nameYesThe product name to generate SEO for

Implementation Reference

  • The core handler function `generateEtsySEO` that validates credentials, constructs a signed payload, calls the Seerxo API, and returns the generated Etsy SEO content (title, description, tags, suggested price, usage).
    async function generateEtsySEO(productName, category = '') {
      if (!userEmail) {
        throw new Error('Email is not set. Run "seerxo configure" first.');
      }
      if (!apiKeyHeader || !apiKeySecret) {
        throw new Error('API key is not set. Run "seerxo configure" first.');
      }
    
      try {
        const payload = {
          product_name: productName,
          category: category || '',
          email: userEmail,
        };
    
        const { signature, timestamp } = generateSignature(payload);
    
        const response = await fetch(getApiEndpoint(), {
          method: 'POST',
          headers: {
            'Content-Type': 'application/json',
            'User-Agent': `seerxo/${clientVersion}`,
            'X-MCP-Signature': signature,
            'X-MCP-Timestamp': timestamp.toString(),
            'X-MCP-Version': clientVersion,
            'X-MCP-API-Key': apiKeyHeader,
          },
          body: JSON.stringify(payload),
        });
    
        if (!response.ok) {
          const error = await response.json().catch(() => ({}));
          throw new Error(
            error.error || error.message || `API error: ${response.status}`
          );
        }
    
        const data = await response.json();
    
        if (!data.success) {
          throw new Error(data.error || 'Content generation failed');
        }
    
        return {
          ...data.data,
          usage: data.usage,
        };
      } catch (error) {
        throw new Error(error.message || 'Failed to generate Etsy SEO content');
      }
    }
  • Input schema for the tool defining required 'product_name' (string) and optional 'category' (string).
    inputSchema: {
      type: 'object',
      properties: {
        product_name: {
          type: 'string',
          description: 'Name of the product to optimize.',
        },
        category: {
          type: 'string',
          description: 'Optional category (e.g., "Home & Living")',
        },
      },
      required: ['product_name'],
    },
  • mcp-server.js:823-851 (registration)
    Registration of the tool in the MCP 'tools/list' RPC method response, including name, description, and input schema.
    } else if (request.method === 'tools/list') {
      const response = {
        jsonrpc: '2.0',
        id: request.id,
        result: {
          tools: [
            {
              name: 'generate_etsy_seo',
              description: 'Generate SEO-optimized Etsy product listings.',
              inputSchema: {
                type: 'object',
                properties: {
                  product_name: {
                    type: 'string',
                    description: 'Name of the product to optimize.',
                  },
                  category: {
                    type: 'string',
                    description: 'Optional category (e.g., "Home & Living")',
                  },
                },
                required: ['product_name'],
              },
            },
          ],
        },
      };
    
      console.log(JSON.stringify(response));
  • mcp-server.js:852-883 (registration)
    MCP 'tools/call' handler that checks the tool name 'generate_etsy_seo', invokes the handler, formats the result as rich text content with usage info, and responds.
    } else if (request.method === 'tools/call') {
      const { name, arguments: toolArgs } = request.params;
    
      if (name === 'generate_etsy_seo') {
        const result = await generateEtsySEO(
          toolArgs.product_name,
          toolArgs.category || ''
        );
    
        const usageInfo = result.usage
          ? `\n\n---\n**Usage:** ${result.usage.current}/${result.usage.limit} generations used (${result.usage.remaining} remaining)`
          : '';
    
        const response = {
          jsonrpc: '2.0',
          id: request.id,
          result: {
            content: [
              {
                type: 'text',
                text: `# Etsy SEO Results for "${toolArgs.product_name}"\n\n## 📝 SEO Title\n${result.title}\n\n## 📄 Product Description\n${result.description}\n\n## 🏷️ Tags (15)\n${result.tags.join(
                  ', '
                )}\n\n## 💰 Suggested Price\n${
                  result.suggested_price_range
                }${usageInfo}`,
              },
            ],
          },
        };
    
        console.log(JSON.stringify(response));
      } else {
  • Helper function that generates the HMAC-SHA256 signature and timestamp for authenticating API requests using the API key secret.
    function generateSignature(payload) {
      const timestamp = Date.now().toString();
      const message = JSON.stringify(payload) + timestamp;
      const signature = crypto
        .createHmac('sha256', apiKeySecret || '')
        .update(message)
        .digest('hex');
      return { signature, timestamp };
    }
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. It mentions a rate limit ('10 generations/month'), which is useful, but fails to describe other critical traits like whether the tool requires authentication, what the output format looks like, or any potential errors. For a generation tool with no annotation coverage, this is insufficient.

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 concise and front-loaded, stating the core purpose in the first sentence and adding a rate limit in the second. Both sentences earn their place by providing essential information without unnecessary details. However, it could be slightly more structured by explicitly separating usage guidelines from behavioral traits.

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 of an SEO generation tool with no annotations and no output schema, the description is incomplete. It lacks details on output format, error handling, authentication needs, and broader context like when to use it effectively. The rate limit hint is helpful but insufficient for a tool that likely produces structured content, leaving significant gaps for an AI agent to understand full behavior.

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?

The input schema has 100% description coverage, with clear documentation for both parameters. The description does not add any additional meaning beyond what the schema provides, such as examples or constraints not covered in the schema. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description neither compensates for gaps nor enhances parameter understanding.

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: 'Generate SEO-optimized Etsy product title, description, and tags.' It specifies the verb ('Generate') and resource ('Etsy product title, description, and tags'), making it easy to understand what the tool does. However, since there are no sibling tools mentioned, it cannot differentiate from alternatives, which prevents a perfect score.

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 minimal usage guidance: it mentions 'Free: 10 generations/month,' which implies a rate limit but does not specify when to use this tool versus alternatives or any prerequisites. There is no explicit context for when or why to invoke it, such as for new product listings or SEO improvements, leaving gaps in practical application advice.

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/semihbugrasezer/etsy-seo-mcp'

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