Skip to main content
Glama

Palmyr

by ai.palmyr

Connect a TikTok account (server-side login)

tiktok_connect

Attach a TikTok account by logging in ON THE SERVER, into that account's own persistent browser profile: returns a connect_url to hand a human, who scans the QR in the TikTok app. The recommended path — the browser that authenticates is the browser that later acts, and every other TikTok tool then works with cookies omitted (no jar to move). The paying wallet becomes the account's owner. Async: poll tiktok_connect_status with the returned token. Costs 0.01 USDC, paid per-action via x402.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoLabel grouping accounts (a niche, a client); tiktok_accounts and tiktok_hooks can scope to it
countryNoISO-2 country the login browser should exit from, e.g. 'US' — TikTok reads a scan from the wrong country as phishing
paymentNobase64 x402 payment payload (X-PAYMENT); omit on first call to receive payment instructions
account_idYesYour identifier for the TikTok account (1-64 chars of A-Z a-z 0-9 . _ -)
proxy_session_idNo

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses critical traits: server-side login, persistent browser profile, async nature, cost (0.01 USDC via x402), and that 'the paying wallet becomes the account's owner'. It also notes the browser-authenticates-acts coupling. It omits details like timeout or failure modes, but is generally transparent about side effects and prerequisites.

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 a single paragraph of about 80 words, front-loaded with the main action 'Attach a TikTok account'. Each sentence adds a new facet: the flow, the rationale, ownership, async polling, and cost. There is no fluff or repetition, making it highly concise while covering essential 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?

This is a complex tool (async, cost, ownership transfer) and no output schema is provided. The description covers the flow, next steps, and cost, and mentions the return of a connect_url and token. It lacks explicit output structure details and error/timeout handling, but given the complexity, it provides a solid foundation. The guidance to poll tiktok_connect_status helps complete the workflow.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 80% (4/5 params have descriptions), so baseline is 3. The description does not add parameter-specific meaning beyond the schema; it only mentions the connect_url and token output, not details about parameters like proxy_session_id (which is undocumented). This is acceptable given the schema coverage, but no extra value is added.

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 states a specific verb+resource: 'Attach a TikTok account by logging in ON THE SERVER'. It clearly distinguishes itself from siblings by detailing the server-side login and persistent browser profile, which is the foundation for other TikTok tools. It also explains the return value (connect_url) and the overall flow, making its purpose unmistakable.

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

Usage Guidelines4/5

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

The description provides clear context: it is 'the recommended path' and explains why, as the authenticating browser will later act and other TikTok tools work without cookies. It also gives sequential guidance to poll tiktok_connect_status with the returned token. However, it does not explicitly name alternative tools or state when NOT to use it, leaving some room for interpretation.

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

All Palmyr toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct resource and action, clearly separated by domain prefixes (card_, email_, phone_, tiktok_). The only potential overlap is phone_read_messages vs wait_for_otp, but wait_for_otp is specifically for OTP extraction and is described as a replacement for hand-rolled polling, making the boundary clear. Status pollers are also domain-specific (card_status, tiktok_connect_status, tiktok_operation_status) and not ambiguous.

Naming Consistency5/5

All tool names follow a consistent snake_case convention with domain-first prefixes (e.g., card_buy, email_send, tiktok_post, phone_temp_number). Even less common names like wait_for_otp and i402_plan are descriptive and stylistically consistent. There are no mixed conventions or vague verbs.

Tool Count4/5

33 tools is above the typical 3-15 range, but the server covers a broad multi-domain purpose (cards, compute, domains, email, phone, TikTok, Twitter, orchestration). Each domain has a focused and coherent set, so the count feels justified rather than bloated. It is slightly high, but not excessively so.

Completeness3/5

Coverage is solid for email, phone, and TikTok, with full lifecycle operations (create, read, extend, delete/cancel where applicable). However, there are notable gaps: compute has only deploy (no list/stop/delete), domains have only check/register (no list/delete), and Twitter has only post (no read/manage). These gaps could force agents to work around missing resource management.

Resources