Get list of configured microCMS services and their available APIs (endpoints). Use this tool first to discover which services are available and find the correct serviceId for other tools. In multi-service mode, serviceId is required for all other tools.

Get a list of contents from microCMS

Get a list of contents with metadata from microCMS Management API. IMPORTANT: Use this tool ONLY when the user message contains "メタ" (meta) or "メタ情報" (metadata). This API returns metadata information such as status, createdBy, updatedBy, reservationTime, closedAt, and customStatus that are not available in the regular content API. For regular content retrieval, use microcms_get_list instead.

Get a specific content from microCMS

Get a specific content with metadata from microCMS Management API. IMPORTANT: Use this tool ONLY when the user message contains "メタ" (meta) or "メタ情報" (metadata). This API returns metadata information such as status, createdBy, updatedBy, reservationTime, closedAt, and customStatus that are not available in the regular content API. For regular content retrieval, use microcms_get_content instead.

Create new content in microCMS and publish it immediately.

Important

Ensure that the "content" you submit strictly adheres to the following specifications. 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

• Image fields require URL string uploaded to microCMS media library (e.g., "https://images.microcms-assets.io/assets/xxx/yyy/sample.png").

• Multiple image fields use array format.

• Rich editor fields expect HTML strings.

• Date fields use ISO 8601 format.

• Select fields use arrays.

• Content reference fields use contentId strings or arrays for multiple references, and you can get contentIds from microcms_get_list tool.

• Custom field exepect below struct:

<field Id in apiFields> {
  "fieldId": "<target custom field id in customFields>"
  "key1": "<value1>",
  "key2": "<value2>",
}

• iframe field (Extension field) expects the following structure for CREATE/UPDATE:

  {
    "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.

Create new content in microCMS and publish it immediately.

Important

Ensure that the "content" you submit strictly adheres to the following specifications. 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

• Image fields require URL string uploaded to microCMS media library (e.g., "https://images.microcms-assets.io/assets/xxx/yyy/sample.png").

• Multiple image fields use array format.

• Rich editor fields expect HTML strings.

• Date fields use ISO 8601 format.

• Select fields use arrays.

• Content reference fields use contentId strings or arrays for multiple references, and you can get contentIds from microcms_get_list tool.

• Custom field exepect below struct:

<field Id in apiFields> {
  "fieldId": "<target custom field id in customFields>"
  "key1": "<value1>",
  "key2": "<value2>",
}

• iframe field (Extension field) expects the following structure for CREATE/UPDATE:

  {
    "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.

Create multiple contents in microCMS at once. This tool processes contents sequentially and continues even if some fail. Results include success/failure status for each content.

Create new content in microCMS and publish it immediately.

Important

Ensure that the "content" you submit strictly adheres to the following specifications. 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

• Image fields require URL string uploaded to microCMS media library (e.g., "https://images.microcms-assets.io/assets/xxx/yyy/sample.png").

• Multiple image fields use array format.

• Rich editor fields expect HTML strings.

• Date fields use ISO 8601 format.

• Select fields use arrays.

• Content reference fields use contentId strings or arrays for multiple references, and you can get contentIds from microcms_get_list tool.

• Custom field exepect below struct:

<field Id in apiFields> {
  "fieldId": "<target custom field id in customFields>"
  "key1": "<value1>",
  "key2": "<value2>",
}

• iframe field (Extension field) expects the following structure for CREATE/UPDATE:

  {
    "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.

Create multiple contents in microCMS at once. This tool processes contents sequentially and continues even if some fail. Results include success/failure status for each content.

Create new content in microCMS and publish it immediately.

Important

Ensure that the "content" you submit strictly adheres to the following specifications. 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

• Image fields require URL string uploaded to microCMS media library (e.g., "https://images.microcms-assets.io/assets/xxx/yyy/sample.png").

• Multiple image fields use array format.

• Rich editor fields expect HTML strings.

• Date fields use ISO 8601 format.

• Select fields use arrays.

• Content reference fields use contentId strings or arrays for multiple references, and you can get contentIds from microcms_get_list tool.

• Custom field exepect below struct:

<field Id in apiFields> {
  "fieldId": "<target custom field id in customFields>"
  "key1": "<value1>",
  "key2": "<value2>",
}

• iframe field (Extension field) expects the following structure for CREATE/UPDATE:

  {
    "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.

Create new content in microCMS and publish it immediately.

Important

Ensure that the "content" you submit strictly adheres to the following specifications. 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

• Image fields require URL string uploaded to microCMS media library (e.g., "https://images.microcms-assets.io/assets/xxx/yyy/sample.png").

• Multiple image fields use array format.

• Rich editor fields expect HTML strings.

• Date fields use ISO 8601 format.

• Select fields use arrays.

• Content reference fields use contentId strings or arrays for multiple references, and you can get contentIds from microcms_get_list tool.

• Custom field exepect below struct:

<field Id in apiFields> {
  "fieldId": "<target custom field id in customFields>"
  "key1": "<value1>",
  "key2": "<value2>",
}

• iframe field (Extension field) expects the following structure for CREATE/UPDATE:

  {
    "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.

Create new content in microCMS and publish it immediately.

Important

Ensure that the "content" you submit strictly adheres to the following specifications. 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

• Image fields require URL string uploaded to microCMS media library (e.g., "https://images.microcms-assets.io/assets/xxx/yyy/sample.png").

• Multiple image fields use array format.

• Rich editor fields expect HTML strings.

• Date fields use ISO 8601 format.

• Select fields use arrays.

• Content reference fields use contentId strings or arrays for multiple references, and you can get contentIds from microcms_get_list tool.

• Custom field exepect below struct:

<field Id in apiFields> {
  "fieldId": "<target custom field id in customFields>"
  "key1": "<value1>",
  "key2": "<value2>",
}

• iframe field (Extension field) expects the following structure for CREATE/UPDATE:

  {
    "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.

Create new content in microCMS and publish it immediately.

Important

Ensure that the "content" you submit strictly adheres to the following specifications. 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

• Image fields require URL string uploaded to microCMS media library (e.g., "https://images.microcms-assets.io/assets/xxx/yyy/sample.png").

• Multiple image fields use array format.

• Rich editor fields expect HTML strings.

• Date fields use ISO 8601 format.

• Select fields use arrays.

• Content reference fields use contentId strings or arrays for multiple references, and you can get contentIds from microcms_get_list tool.

• Custom field exepect below struct:

<field Id in apiFields> {
  "fieldId": "<target custom field id in customFields>"
  "key1": "<value1>",
  "key2": "<value2>",
}

• iframe field (Extension field) expects the following structure for CREATE/UPDATE:

  {
    "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.

Change content publication status in microCMS (Management API). Can change status between PUBLISH (published) and DRAFT (draft). Note: Only transitions between "published" and "draft" are supported.

Change content creator in microCMS (Management API). Updates the createdBy field of a content item to a specified member ID. Member ID can be found in the member detail screen in the management console.

Delete content from microCMS

Get media files from microCMS (Management API). Returns media information including URLs, dimensions for images. Supports pagination via token (15-second validity). Requires media retrieval permissions.

Upload media files to microCMS using JS SDK (Management API). Supports two methods: 1) Upload file data (base64) with filename and mimeType, 2) Upload from external URL. Returns microCMS asset URL. Requires media upload permissions. Available on Team, Business, Advanced, and Enterprise plans.

Delete media files from microCMS (Management API). Supports deletion of both images and files. Requires media deletion permissions. Note: Media referenced by content cannot be deleted.

Get API schema information from microCMS Management API. In relation and relationList field, you can get its schema using referencedApiEndpoint and microcms_get_api_info tool.

Get list of all available APIs (endpoints) from microCMS Management API. Returns API name, endpoint, and type (list/object) for each API.

Get a specific member from microCMS Management API. Returns member information including ID, name, email, and MFA status.