Skip to main content
Glama
SwipeBuilder-io

SwipeBuilder MCP Server

by SwipeBuilder-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SWIPEBUILDER_API_KEYYesYour API key. Starts with sb_live_ or sb_test_. Can also be passed per-tool call.
SWIPEBUILDER_API_URLNoAPI base URL (for testing)https://api.swipebuilder.io/v1

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_swipesA
Get swipes from your swipe file.

Args:
    api_key: Your SwipeBuilder API key (sb_live_xxx or sb_test_xxx). 
             Optional if SWIPEBUILDER_API_KEY env var is set.
    platform: Filter by platform (facebook, tiktok, instagram, linkedin, google)
    format: Filter by format (image, video, carousel)
    limit: Number of results (1-100, default 50)
    cursor: Pagination cursor from previous response

Returns:
    Dictionary with swipes data, pagination info, and credit usage

Credit Usage: 1 credit per swipe returned
get_swipeB
Get a single swipe by ID.

Args:
    swipe_id: The ID of the swipe to retrieve
    api_key: Your SwipeBuilder API key. Optional if SWIPEBUILDER_API_KEY env var is set.

Returns:
    Dictionary with swipe data or error message

Credit Usage: 1 credit
get_collectionsA
Get your collections (folders).

Args:
    api_key: Your SwipeBuilder API key. Optional if SWIPEBUILDER_API_KEY env var is set.
    parent_id: Filter by parent ('root' for root-level, collection ID for children, None for all)
    limit: Number of results (1-100, default 50)
    cursor: Pagination cursor from previous response

Returns:
    Dictionary with collections data and pagination info

Credit Usage: No credits consumed
get_collectionB
Get a single collection by ID.

Args:
    collection_id: The ID of the collection to retrieve
    api_key: Your SwipeBuilder API key. Optional if SWIPEBUILDER_API_KEY env var is set.

Returns:
    Dictionary with collection data or error message

Credit Usage: No credits consumed
get_collection_itemsB
Get items (swipes) in a collection.

Args:
    collection_id: The ID of the collection
    api_key: Your SwipeBuilder API key. Optional if SWIPEBUILDER_API_KEY env var is set.
    limit: Number of results (1-100, default 50)
    cursor: Pagination cursor from previous response

Returns:
    Dictionary with collection info, items data, and pagination

Credit Usage: 1 credit per swipe returned
get_usageA
Get your API credit usage for the current month.

Args:
    api_key: Your SwipeBuilder API key. Optional if SWIPEBUILDER_API_KEY env var is set.

Returns:
    Dictionary with usage statistics including:
    - credits_used: Credits consumed this month
    - credits_limit: Monthly credit limit
    - credits_remaining: Credits still available
    - period_start: Start of billing period
    - period_end: End of billing period

Credit Usage: No credits consumed

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 6 tools

Disambiguation5/5

Every tool has a clearly distinct purpose with no ambiguity. The tools are organized around specific resources (collections, swipes, usage) and actions (get single item, get list, get usage), making it easy for an agent to select the right tool for each task without confusion.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case, specifically 'get_' followed by the resource name (e.g., get_collection, get_swipes). This predictability enhances readability and usability across the entire tool set.

Tool Count5/5

With 6 tools, the server is well-scoped for its purpose of accessing SwipeBuilder data. Each tool serves a clear and necessary function—retrieving collections, swipes, and usage information—without being overly sparse or bloated, fitting typical expectations for such an API.

Completeness4/5

The tool surface provides comprehensive read-only coverage for the domain, including retrieval of collections, items within collections, swipes, and usage data. A minor gap exists in the lack of create, update, or delete operations, but this is likely intentional for a data access server, and agents can still perform core workflows effectively.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources