Skip to main content
Glama
Sign In
slidecold-mcp

slidecold-mcp

by slidecold
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Import members

import_audience_members

Import audience members from a single username, a username array, or a CSV file; existing members remain untouched.

Instructions

Import members. Required API key scope: audiences:write. POST /audiences/{id}/import Three input forms: JSON with a single username (plus optional profile fields), JSON with a usernames string array, or a multipart CSV file (required column username/instagram_username/ ig_username; optional full_name, followers, following, bio, last_post_date). Leading @ is stripped. Max 10,000 per import. Existing members are left untouched but still counted in imported.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "import_audience_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPath parameter `id`.
bodyNoJSON request body.
file_pathNoPath to a local file, uploaded as the multipart `file` field. Use either this or `body`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: required OAuth scope (audiences:write), a hard 10,000-per-import ceiling, '@' prefix normalization, and the important semantic that existing members are skipped yet still counted in the `imported` total. That last point is exactly the kind of dedupe/merge behavior an agent cannot infer from readOnlyHint=false / idempotentHint=false / destructiveHint=false.

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?

Front-loaded with scope and endpoint, then the input forms, then limits and edge behavior. The opening "Import members." merely restates the title, but every remaining sentence carries information.

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?

Complete for a write tool with three mutually exclusive input modes: it covers auth, size limits, accepted columns, and merge semantics. It stops short of saying whether one malformed row aborts the whole batch, or what the failure response looks like, but no output schema exists to offset that.

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?

Schema coverage is 100%, so baseline is 3, but the description earns more by documenting things the schema does not: accepted CSV column names (username/instagram_username/ig_username), optional CSV columns, and the '@' stripping rule. It also clarifies that `file_path` maps to the multipart `file` field.

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?

States a specific verb and resource ("Import members") and pins it to an audience via the POST /audiences/{id}/import endpoint, which distinguishes it from create_audience and list_audience_members. No sibling is named explicitly, which keeps it just short of a 5.

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

Usage Guidelines3/5

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

The three input forms and the 'use either this or body' constraint imply when to pick each variant, but the description never says when to prefer bulk import over create_audience or per-member adds, nor any when-not-to-use condition.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools