Skip to main content
Glama

tiktok.search_photos

Search TikTok photo posts by keyword. Requires query. Pass cursor from a previous response to fetch the next page.

Cost = 5 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of items to return (max 30).
queryYesSearch keywords.
cursorNoPagination cursor from a previous response.
regionNoRegion code (for example us, jp, kr).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
msgNoUpstream status message.
codeNoUpstream status code (0 = success).
dataNoCapability-specific payload from the upstream provider.
processed_timeNoUpstream processing time in seconds.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / properties / processed_time / anyOf
      Previous value: -[
      -  {},
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations are present, so the description carries the behavioral burden. It discloses pagination behavior ('Pass cursor from a previous response to fetch the next page') and cost ('Cost = 5 tokens'), but does not mention authentication, side effects, or explicitly confirm read-only behavior.

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?

Description is three short sentences: purpose, usage requirement, and cost. Every sentence adds value and key facts are front-loaded with no filler.

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?

Output schema is present, so return values are covered elsewhere. The description covers required query, pagination, and cost, making it sufficient for an agent to invoke the tool and page through results, though it omits count/region customization (already in schema).

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 100%, so query, count, cursor, and region are already documented. The description adds 'Requires query' and cursor usage, but these mostly reinforce the schema rather than adding new parameter semantics.

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?

Description states exactly 'Search TikTok photo posts by keyword', naming the specific action, platform, and content type. This clearly distinguishes it from siblings like tiktok.search_videos and tiktok.search_users.

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?

Description gives clear context: searching photo posts by keyword, with query required and pagination via cursor. It does not explicitly name alternatives or exclusions, but the specific content type makes the appropriate use obvious next to video/user search siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.