Skip to main content
Glama
Sign In
PostKing MCP Server

PostKing MCP Server

by bitsandtea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

import_assets_csv

Batch-import up to 50 public URLs into the brand library. Use the detail parameter to control the verbosity of the returned asset list.

Instructions

Batch-import up to 50 assets by providing an array of public URLs. All are added to the brand library. Supports detail param for the returned asset list.

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": {
      "urls": "<urls>"
    },
    "name": "import_assets_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesArray of public URLs to import
detailNoVerbosity of returned item(s): "short" = id + primary label + status (cheap list scan); "medium" = key summary fields + counts (a useful glance); "full" = the complete object. Default "short". Lists default to "short" — to zoom into one item, call its get/view tool with detail="medium" or "full".short
brandIdNoBrand ID (defaults to active brand)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.7

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the batch limit (50), input type (public URLs), destination (brand library), and detail param effect. Missing are potential partial failure behavior, error handling, or whether the operation is atomic or synchronous.

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 just two sentences, front-loaded with the key action and limit. Every part adds value; no fluff.

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?

Given the rich schema and moderate complexity, the description covers most essentials: batch size, destination, and detail param. However, without an output schema, it doesn't clarify return structure or failure reporting, which is a slight gap for a batch mutation tool.

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%, and the schema already provides detailed descriptions for all three parameters. The description adds context about public URLs and brand library but does not enhance the semantic meaning of individual parameters beyond the schema.

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 clearly states 'Batch-import up to 50 assets by providing an array of public URLs' which gives a specific verb, resource, and scope. It distinguishes itself from the sibling tool import_asset_from_url by emphasizing batch import and array input.

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 implies usage for batch import scenarios ('Batch-import up to 50 assets') and notes all are added to the brand library. However, it does not explicitly name alternatives or state when not to use this tool, such as for single imports.

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