Skip to main content
Glama

get_twitterapi_pricing

Retrieve Twitter API pricing details including credit costs per endpoint, rate limits by balance level, and pricing tiers for budget planning.

Instructions

Get TwitterAPI.io pricing information: credit system, endpoint costs, QPS limits.

USE THIS WHEN: You need to know API costs, credit calculations, or rate limits. RETURNS: Pricing tiers, credit costs per endpoint, QPS limits by balance level.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
costsNo
notesNo
markdownYes
qps_limitsNo
minimum_chargeNo
credits_per_usdNo

Implementation Reference

  • Handler implementation for get_twitterapi_pricing tool. Retrieves pricing and QPS limits from loaded docs data, constructs a detailed markdown response covering credits per USD, endpoint costs, minimum charge, QPS limits by tier, notes, and cost comparison. Returns formatted success response with structured content matching the output schema.
        case "get_twitterapi_pricing": {
          const pricing = data.pricing || {};
          const qps = data.qps_limits || {};
    
          const notes = [
            'Credits never expire',
            'Bonus credits valid for 30 days',
            'Up to 5% discount on bulk purchases',
            'List endpoints: 150 credits/request',
            '~97% cheaper than official Twitter API'
          ];
    
          const markdown = `# TwitterAPI.io Pricing
    
    ## Credit System
    - **1 USD = ${pricing.credits_per_usd?.toLocaleString() || "100,000"} Credits**
    
    ## Endpoint Costs
    ${Object.entries(pricing.costs || {}).map(([k, v]) => `- **${k}**: ${v}`).join("\n")}
    
    ## Minimum Charge
    ${pricing.minimum_charge || "15 credits ($0.00015) per request"}
    
    ## QPS (Queries Per Second) Limits
    
    ### Free Users
    ${qps.free || "1 request per 5 seconds"}
    
    ### By Balance Level
    ${Object.entries(qps.paid || {}).map(([k, v]) => `- **${k.replace(/_/g, " ")}**: ${v}`).join("\n")}
    
    ## Important Notes
    - Credits never expire
    - Bonus credits valid for 30 days
    - Up to 5% discount on bulk purchases
    - List endpoints: 150 credits/request
    
    ## Cost Comparison
    TwitterAPI.io is **~97% cheaper** than official Twitter API.
    - Twitter Pro: $5,000/month
    - TwitterAPI.io equivalent: ~$150/month`;
    
          return formatToolSuccess(markdown, {
            credits_per_usd: pricing.credits_per_usd || 100000,
            minimum_charge: pricing.minimum_charge || "15 credits ($0.00015) per request",
            costs: pricing.costs || {},
            qps_limits: {
              free: qps.free || "1 request per 5 seconds",
              paid: qps.paid || {}
            },
            notes,
            markdown
          });
        }
  • index.js:1567-1626 (registration)
    Tool registration in ListToolsRequestSchema handler, including name, description, empty inputSchema (no parameters required), and detailed outputSchema defining the structured response fields for pricing data.
          name: "get_twitterapi_pricing",
          description: `Get TwitterAPI.io pricing information: credit system, endpoint costs, QPS limits.
    
    USE THIS WHEN: You need to know API costs, credit calculations, or rate limits.
    RETURNS: Pricing tiers, credit costs per endpoint, QPS limits by balance level.`,
          inputSchema: {
            type: "object",
            properties: {},
          },
          outputSchema: {
            type: "object",
            properties: {
              credits_per_usd: { type: "number" },
              minimum_charge: { type: "string" },
              costs: { type: "object", additionalProperties: { type: "string" } },
              qps_limits: {
                type: "object",
                properties: {
                  free: { type: "string" },
                  paid: { type: "object", additionalProperties: { type: "string" } }
                }
              },
              notes: { type: "array", items: { type: "string" } },
              markdown: { type: "string" }
            },
            required: ["markdown"]
          }
        },
        {
          name: "get_twitterapi_auth",
          description: `Get TwitterAPI.io authentication guide: API key usage, headers, code examples.
    
    USE THIS WHEN: You need to set up authentication or see request examples.
    RETURNS: API key header format, base URL, cURL/Python/JavaScript examples.`,
          inputSchema: {
            type: "object",
            properties: {},
          },
          outputSchema: {
            type: "object",
            properties: {
              header: { type: "string" },
              base_url: { type: "string" },
              dashboard_url: { type: "string" },
              examples: {
                type: "object",
                properties: {
                  curl: { type: "string" },
                  python: { type: "string" },
                  javascript: { type: "string" }
                }
              },
              markdown: { type: "string" }
            },
            required: ["header", "base_url", "markdown"]
          }
        },
        ],
      };
    });
  • Output schema definition for get_twitterapi_pricing tool, specifying the structure of the returned pricing data including credits_per_usd, minimum_charge, costs object, qps_limits nested object, notes array, and markdown string.
        type: "object",
        properties: {
          credits_per_usd: { type: "number" },
          minimum_charge: { type: "string" },
          costs: { type: "object", additionalProperties: { type: "string" } },
          qps_limits: {
            type: "object",
            properties: {
              free: { type: "string" },
              paid: { type: "object", additionalProperties: { type: "string" } }
            }
          },
          notes: { type: "array", items: { type: "string" } },
          markdown: { type: "string" }
        },
        required: ["markdown"]
      }
    },
  • SLO (Service Level Objective) configuration for get_twitterapi_pricing tool in the logger metrics, defining performance targets: 5ms target, 20ms acceptable, 50ms alert threshold.
    get_twitterapi_pricing: { target: 5, acceptable: 20, alert: 50 },
Behavior4/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. It discloses behavioral traits by specifying what information is retrieved (pricing tiers, credit costs, QPS limits) and implies it's a read-only operation without destructive effects. However, it doesn't mention potential rate limits or authentication needs for the tool itself.

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 well-structured and front-loaded, with three concise sections: purpose, usage guidelines, and returns. Each sentence earns its place by adding specific value without redundancy, making it easy to scan and understand.

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

Completeness5/5

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

Given the tool's low complexity (0 parameters, no annotations), the description is complete. It clearly states purpose, usage, and return values, and with an output schema present, it doesn't need to detail return formats. This adequately covers all necessary context for a simple informational tool.

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 adds value by clarifying the scope of information returned, which compensates for the lack of parameters. Baseline is 4 for 0 parameters, as it provides useful context beyond the schema.

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 specific action ('Get') and resource ('TwitterAPI.io pricing information'), with explicit details on what it covers: credit system, endpoint costs, and QPS limits. It distinguishes from siblings by focusing on pricing, unlike tools for auth, endpoints, guides, URLs, or docs.

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?

The 'USE THIS WHEN' section explicitly states when to use this tool: for API costs, credit calculations, or rate limits. This provides clear context and distinguishes it from alternatives, such as tools for endpoint details or documentation search.

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/dorukardahan/twitterapi-io-mcp'

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