add some apis and iframe field description

Author: himaratsu

manifest.json

@@ -2,7 +2,7 @@
   "manifest_version": "0.2",
   "name": "microcms-mcp-server",
   "display_name": "microCMS MCP Server",
-  "version": "0.6.0",
+  "version": "0.7.0",
   "description": "microCMSのMCP Serverです。LLMから直接コンテンツの取得や入稿ができます。",
   "icon": "assets/icon.png",
   "author": {

src/constants.ts

@@ -3,8 +3,9 @@ export const FIELD_FORMATS_DESCRIPTION = `
 
   ## Important
   Ensure that the "content" you submit strictly adheres to the following specifications.
-  In particular, take extra care when handling custom fields, as mistakes are common in their structure. 
+  In particular, take extra care when handling custom fields and iframe fields, as mistakes are common in their structure. 
   Read the instructions thoroughly and construct the data precisely as described.
+  In particular, for extended fields (iframe fields), you need to take care to call microcms_get_list tool beforehand, and set its structure to the "data" field (Detail is described below).
   
   ## Field type specifications
   
@@ -22,4 +23,19 @@ export const FIELD_FORMATS_DESCRIPTION = `
     "key2": "<value2>",
   }
   \`\`\`
+* iframe field (Extension field) expects the following structure for CREATE/UPDATE:
+\`\`\`json
+  {
+    "id": "some-id",
+    "title": "some-title",
+    "description": "some-description",
+    "imageUrl": "https://images.microcms-assets.io/assets/xxxx/yyyy/{fileName}.png",
+    "updatedAt": "2024-01-01T00:00:00Z",
+    "data": { "key1": "value1", "key2": "value2" }
+  }
+\`\`\`
+  * **IMPORTANT**: When retrieving content via API, only the "data" object content is returned (without the wrapper).
+  * **IMPORTANT**: When creating/updating content, you MUST provide the full structure including id, title, description, imageUrl, updatedAt, and data.
+  * To understand the "data" structure, ALWAYS use microcms_get_list to retrieve existing content first and examine the field structure.
+  * "id", "title", "description", "imageUrl" are metadata displayed in the admin screen and are not included in the API GET response.
   `;

src/tools/get-content-meta.ts

@@ -35,3 +35,4 @@ export async function handleGetContentMeta(params: ToolParameters) {
   return await getContentManagement(endpoint, contentId);
 }
 
+

src/tools/patch-content-created-by.ts

@@ -46,3 +46,4 @@ export async function handlePatchContentCreatedBy(
   return { message: `Content ${contentId} creator changed to ${createdBy}`, id: result.id };
 }
 
+

src/tools/patch-content-status.ts

@@ -47,3 +47,4 @@ export async function handlePatchContentStatus(
   return { message: `Content ${contentId} status changed to ${status}` };
 }
 
+