Skip to main content
Glama
Sign In
Grinv

AniList MCP Server

by Grinv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Post a message activity

post_message_activity

Post or update a public message-style activity on another AniList user's profile; use recipient ID and message text, or an activity ID to edit. This is not a private DM.

Instructions

[Requires login] Post a new message-style activity to another AniList user's profile, or update an existing one by passing its id. Despite the name, this is NOT a private DM — like post_text_activity, it's publicly visible on both users' activity feeds/profiles to anyone who can view them. This is a limitation of this tool, not AniList itself: AniList's underlying mutation does accept a private argument, but this tool doesn't expose it, so every message sent through it is public. Don't use it for anything the sender expects to stay confidential.

Input Schema

NameRequiredDescriptionDefault
idNoActivity ID to update instead of creating a new post.
messageYesThe message text to post (per AniList's own schema: 2-10000 characters).
recipientIdYesAniList numeric user ID of the message recipient (resolve a username via search_user first).

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 / message / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / activity / properties / message / type
      Added value: +[
+  "string",
+  "null"
+]
  3. Changed8 schema fields changedv0.7.1
    • addedInput schema / properties / id / exclusiveMinimum
      Added value: +0
    • removedInput schema / properties / id / minimum
      Removed value: --2147483648
    • addedInput schema / properties / recipientId / exclusiveMinimum
      Added value: +0
    • removedInput schema / properties / recipientId / 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 / message / description
      Previous value: -"The message text to post."New value: +"The message text to post (per AniList's own schema: 2-10000 characters)."
    • addedInput schema / properties / message / maxLength
      Added value: +10000
    • changedInput schema / properties / message / minLength
      Previous value: -1New value: +2
  5. Addedv0.2.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare this is a non-readonly, open-world, non-destructive mutation, and the description adds substantial context: login is required, posts are publicly visible on both profiles/feeds, and the tool omits AniList's underlying `private` argument. These are exactly the behavioral details an agent needs for privacy-sensitive use.

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 front-loaded with the login requirement and core action, then spends its remaining sentences on the critical public-visibility warning. There is no filler; each sentence adds either a usage constraint or a privacy clarification.

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?

The tool is a mutation with an output schema, full parameter documentation, and annotations covering safety. The description fills the remaining critical gap — public visibility and lack of a private option — so an agent has everything needed to invoke it responsibly.

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 the schema already documents `id`, `message`, and `recipientId` thoroughly, including the username-to-ID resolution hint. The description adds the high-level update-via-`id` behavior but no new parameter-level meaning 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 states a specific verb and resource: posting a message-style activity to another AniList user's profile, or updating an existing one via `id`. It explicitly distinguishes this from a private DM and from `post_text_activity`, so an agent can identify the tool without opening the 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?

It gives a clear when-not condition: do not use it for confidential content because the output is public. It also mentions `post_text_activity` as a similar public posting tool, but does not explicitly compare when to choose one over the other.

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