Skip to main content
Glama
artem-amplemarket

Amplemarket Knowledge Base MCP Server

amplemarket_get_all_articles

Retrieve all available articles from the Amplemarket knowledge base to browse titles, IDs, and metadata before accessing specific content.

Instructions

PRIMARY TOOL: Get all articles from the Amplemarket knowledge base. Returns complete list of article titles, IDs, and metadata. Use this first to browse available articles, then use amplemarket_get_article to get full content of specific articles. No search needed - this shows everything available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that fetches all Amplemarket KB articles using PylonAPI, filters published/unpublished, maps to metadata, and returns formatted JSON response.
    export async function handleKbGetArticles(pylonClient: PylonAPI, args: unknown) {
      try {
        const articles = await pylonClient.getAmplemarketArticles();
        
        // Separate published and unpublished articles
        const publishedArticles = articles.filter(article => article.is_published);
        const unpublishedArticles = articles.filter(article => !article.is_published);
        
        // Return only essential metadata to avoid response size limits
        const mapArticle = (article: any) => ({
          id: article.id,
          title: article.title,
          slug: article.slug,
          identifier: article.identifier,
          is_published: article.is_published,
          last_published_at: article.last_published_at,
          // Exclude the large current_published_content_html field
        });
        
        const publishedData = publishedArticles.map(mapArticle);
        const unpublishedData = unpublishedArticles.map(mapArticle);
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({
                summary: {
                  total: articles.length,
                  published_count: publishedArticles.length,
                  unpublished_count: unpublishedArticles.length,
                  knowledge_base: 'Amplemarket Knowledge Base'
                },
                published_articles: publishedData,
                unpublished_articles: unpublishedData,
                note: 'Full article content not included - use amplemarket_get_article for specific article content'
              }, null, 2)
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error getting Amplemarket articles: ${error instanceof Error ? error.message : 'Unknown error'}`
            }
          ],
          isError: true
        };
      }
    }
  • Tool schema defining name, description, and empty input schema (no parameters required).
    export const kbGetArticlesTool: Tool = {
      name: 'amplemarket_get_all_articles',
      description: 'PRIMARY TOOL: Get all articles from the Amplemarket knowledge base. Returns complete list of article titles, IDs, and metadata. Use this first to browse available articles, then use amplemarket_get_article to get full content of specific articles. No search needed - this shows everything available.',
      inputSchema: {
        type: 'object',
        properties: {},
        additionalProperties: false
      }
    };
  • src/index.ts:51-52 (registration)
    Registration of the tool handler in the MCP server's CallToolRequestSchema handler switch statement.
    case 'amplemarket_get_all_articles':
      return await handleKbGetArticles(pylonClient, request.params.arguments);
  • src/index.ts:39-43 (registration)
    Registration of the tool in the ListToolsRequestSchema handler, making it discoverable by MCP clients.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [kbGetArticleTool, kbGetCollectionTool, kbGetArticlesTool],
      };
    });
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by stating it 'Returns complete list of article titles, IDs, and metadata' and 'No search needed - this shows everything available', which clarifies scope and output. It doesn't mention rate limits, permissions, or pagination, but provides useful behavioral context.

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

Conciseness5/5

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

The description is front-loaded with the primary purpose, followed by usage guidance, all in three concise sentences with zero waste. Every sentence earns its place by adding value.

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

Completeness4/5

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

Given 0 parameters, no annotations, and no output schema, the description is complete enough for a simple list tool: it states purpose, output format ('titles, IDs, and metadata'), and usage context. It could mention response format details, but it's largely adequate.

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 0 parameters with 100% schema description coverage, so the baseline is 4. The description adds no parameter information (as there are none), which is appropriate and doesn't detract from the high baseline.

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

Purpose5/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 all articles from the Amplemarket knowledge base' with specific verb ('Get') and resource ('articles'), and distinguishes it from its sibling 'amplemarket_get_article' by explaining this tool returns metadata while the sibling returns full content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance is provided: 'Use this first to browse available articles, then use amplemarket_get_article to get full content of specific articles' and 'No search needed - this shows everything available', clearly indicating when to use this tool versus alternatives.

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/artem-amplemarket/amplemarket-pylon-mcp'

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