MCP: Content plugin is unable to recognise the md5 parsed name property and skipping the executeTool method

Created on 11 April 2025, 14 days ago

Problem/Motivation

Below is the request being sent from claude desktop , the name

{
  "jsonrpc": "2.0",
  "id": 5713001017200931,
  "method": "tools/call",
  "params": {
    "name": "content_85d467739a1b4ba46a9b8c4c9516704c",
    "arguments": {
      "contentType": "article",
      "filters": [
 
      ],
      "limit": 50
    }
  }
}

The name property: content_85d467739a1b4ba46a9b8c4c9516704c is not getting recognised by the 'content' MCP plugin. This i think due to the md5 encoding , but this is skipping the executeTool method.

Donโ€™t we need to add a condition based on this in executetool method

Steps to reproduce

Using Postman send the below json reqest to the MCP endpoint and it will work but the above dosent.

{
  "jsonrpc": "2.0",
  "id": 5713001017200931,
  "method": "tools/call",
  "params": {
    "name": "content_search-content",
    "arguments": {
      "contentType": "article",
      "filters": [
      
      ],
      "limit": 50
    }
  }
}

Proposed resolution

There should be check on the hashed value as well in the content MCP plugin.

Remaining tasks

User interface changes

API changes

Data model changes

๐Ÿ› Bug report
Status

Active

Version

1.0

Component

Code

Created by

๐Ÿ‡ฎ๐Ÿ‡ณIndia vakulrai

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024