Skip to main content
Glama
Sign In
twikit-mcp

twikit-mcp

by tangivis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

edit_list

Update a Twitter List's metadata by changing its name, description, or privacy setting. Provide the list ID and at least one field to modify; leave description blank to clear it.

Instructions

Edit a Twitter List's metadata.

At least one of name, description, or is_private must be provided. Pass an empty string for description to clear it.

Args: list_id: The list ID (required). name: New name for the list. description: New description (empty string clears it). is_private: True to make private, False to make public.

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": {
      "list_id": "<list_id>"
    },
    "name": "edit_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
list_idYes
is_privateNo
descriptionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.39
    • addedInput schema / properties / list_id / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "string"
+  }
+]
    • removedInput schema / properties / list_id / type
      Removed value: -"string"
  2. First observedv0.1.33

TDQS

A4.3/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 clearly indicates this is a mutation ('Edit') and additionally discloses the empty-string-clears-description behavior. However, it omits potential side effects, permission requirements, or error scenarios, leaving some behavioral aspects undisclosed.

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 succinct and well-structured: one sentence for purpose, one for constraints, one for special behavior, then a clean parameter list. No redundant filler; every sentence contributes actionable 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?

For a simple edit tool with an output schema, the description covers the essential inputs and constraints. The lack of mention of return values is mitigated by the existence of an output schema. It could add permission context or error handling, but overall it's largely complete for this complexity.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate. It explains each parameter: list_id is required, name is the new name, description can be cleared with an empty string, and is_private sets privacy. The empty-string behavior and the at-least-one-field constraint add meaning beyond the raw 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 the action 'Edit a Twitter List's metadata' and lists the editable fields (name, description, is_private). This distinguishes it from sibling tools like create_list (create), get_list (retrieve), and add_list_member (add member), making the purpose unambiguous.

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?

Provides explicit usage prerequisites: 'At least one of name, description, or is_private must be provided' and explains how to clear the description. While it doesn't explicitly compare to alternatives, the context of editing an existing list is clear from the purpose and the parameter details.

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