Skip to main content
Glama
Grinv

AniList MCP Server

by Grinv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Post a text activity

post_text_activity

Create a new text-status update on your AniList profile or modify an existing post by passing its activity ID.

Instructions

[Requires login] Post a new text-status update to the authenticated user's own AniList profile, or update an existing one by passing its id.

Input Schema

NameRequiredDescriptionDefault
idNoActivity ID to update instead of creating a new post.
textYesThe text to post (per AniList's own schema: 5-10000 characters).

Output Schema

NameRequiredDescriptionDefault
activityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.11.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changedv0.9.0
    • removedOutput schema / properties / activity / properties / text / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / activity / properties / text / type
      Added value: +[
+  "string",
+  "null"
+]
  3. Changed6 schema fields changedv0.7.1
    • addedInput schema / properties / id / exclusiveMinimum
      Added value: +0
    • removedInput schema / properties / id / minimum
      Removed value: --2147483648
    • addedOutput schema / properties / activity / properties / id / exclusiveMinimum
      Added value: +0
    • changedOutput schema / properties / activity / properties / id / maximum
      Previous value: -9007199254740991New value: +2147483647
    • removedOutput schema / properties / activity / properties / id / minimum
      Removed value: --9007199254740991
    • changedOutput schema / properties / activity / properties / siteUrl / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "format": "uri",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
  4. Changed3 schema fields changedv0.5.0
    • changedInput schema / properties / text / description
      Previous value: -"The text to post."New value: +"The text to post (per AniList's own schema: 5-10000 characters)."
    • addedInput schema / properties / text / maxLength
      Added value: +10000
    • changedInput schema / properties / text / minLength
      Previous value: -1New value: +5
  5. Addedv0.3.0
  6. Removedv0.2.0
  7. First observedv0.1.5

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=false, openWorld=true and destructive=false. The description adds genuinely non-redundant context: authentication is required, the target is restricted to the caller's own profile (no posting to other users), and the id parameter switches the call from create to mutate semantics.

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?

One sentence, front-loaded with the login prerequisite and the primary action, with the update variant following as a compact clause. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained. For a 2-parameter mutation the description covers auth, target scope, and the create-vs-update branch, leaving nothing an agent needs before calling it correctly.

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%, including the 5-10000 character range and the id-as-update semantics, so the schema already carries parameter meaning. The description's phrasing about `id` largely restates the schema's own 'update instead of creating a new post' wording rather than adding new detail.

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?

States a specific verb (post/update) and resource (text-status update on AniList profile) with scope clearly limited to the authenticated user's own profile. The 'text-status' qualifier distinguishes it from the sibling post_message_activity without opening either schema.

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?

Explicitly splits the two modes: create a new post by default, or update an existing one by passing `id`. The '[Requires login]' prefix gives an actionable prerequisite. It stops short of naming alternatives (post_message_activity, delete_activity) for cases where the agent wants a non-text activity or removal.

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