FeedMob MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FEEDMOB_API_TOKEN | Yes | Your FeedMob API token | |
| FEEDMOB_API_BASE_URL | No | Base URL for the FeedMob Assistant Internal API (optional, defaults to https://assistant.feedmob.ai) | https://assistant.feedmob.ai |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_clientsC | List clients with optional filters. Returns client names, IDs, and legacy IDs. |
| get_clientB | Get detailed information about a specific client by ID. |
| list_client_documentsC | List documents associated with clients. Can filter by client ID, title, or category. |
| list_partnersB | List partners (vendors/ad networks) with optional filters. |
| get_partnerC | Get detailed information about a specific partner by ID. |
| list_partner_categoriesB | List all partner categories with their IDs. |
| list_partner_documentsB | List documents associated with partners. |
| list_campaignsC | List campaigns with optional filters. Campaigns represent advertising campaigns for clients. |
| get_campaignC | Get detailed information about a specific campaign by ID. |
| list_playbooksB | List playbooks accessible to the current user. Playbooks are guides and documentation. |
| get_playbookB | Get detailed information about a playbook, including its list of items. |
| get_playbook_itemC | Get the full content of a specific playbook item. |
| list_mobile_appsC | List mobile apps with optional filters. |
| get_mobile_appC | Get detailed information about a specific mobile app by ID. |
| list_click_urlsB | List click URLs (tracking links) used for campaign attribution. |
| get_click_urlC | Get detailed information about a specific click URL by legacy ID. |
| get_daily_metricsB | Get aggregated daily metrics as a time-series suitable for charting. Returns data for the specified metric over a date range. |
| list_podsB | List all pods. Pods are organizational units that group clients and team members. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Every tool has a clearly distinct purpose targeting specific resources (campaigns, clients, metrics, etc.) with no overlap. The 'get_' tools retrieve single entities by ID, while 'list_' tools return collections with filters, creating a clean separation. An agent can easily distinguish between tools like get_campaign and list_campaigns based on whether they need details or a filtered list.
All tools follow a consistent verb_noun pattern with perfect uniformity. The 'get_' prefix is used for retrieving single entities, and 'list_' for collections, applied consistently across all resources (campaigns, clients, partners, etc.). This predictable naming makes it easy for agents to infer tool purposes and navigate the set.
With 18 tools, the count is slightly high but reasonable for a comprehensive advertising/campaign management domain. It covers multiple resource types (campaigns, clients, partners, playbooks, etc.) with both detail and listing operations, avoiding bloat. A minor reduction might streamline it, but each tool earns its place by serving a distinct function.
The tool set provides strong coverage for a FeedMob advertising platform, including core CRUD-like operations (get and list) for key entities like campaigns, clients, and partners. Minor gaps exist, such as missing update/delete tools or campaign creation, but agents can work around these for read-heavy use cases. The inclusion of metrics, documents, and playbooks adds useful breadth.