Of course. Here is a complete, professionally written bug report in English based on the issue you've encountered. You can copy and paste this directly into the GitHub issue page you have open.

Title:
Bug: Fails to create database pages due to an internally generated, malformed 'icon' property.

Description:
Bug Description

When attempting to add a new page (entry) to a Notion database, the notion-mcp-server fails. The error log indicates that the Notion API is rejecting the request because of an incorrectly formatted icon property. Further investigation reveals this malformed icon property is being added to the API request by the MCP server itself by default, even when no icon is requested in the prompt.

Steps to Reproduce:

Successfully configure and connect to the notion-mcp-server.

Provide the tool with a valid Notion Database ID to work with.

Issue a simple prompt to create a new page, for example: "Add a new entry to the database with the name 'Test Entry'"

Observe the API error in the debug logs.

Expected Behavior:

A new page/entry should be successfully created in the target Notion database.

Actual Behavior:

The operation fails. The debug log shows a repeated API error:
API-post-page (notionApi MCP Server) {...} unknown format "json" ignored in schema at path "#/properties/icon"

The assistant then reports that it is unable to save the page due to this internal error.

Investigation & Additional Context:

To isolate the issue, I explicitly asked the assistant to create a page without an icon: "Please try again, but do not set any icon for the entry. Skip the icon field."

The assistant responded that it had never attempted to set an icon field in any of its previous attempts. It confirmed that the error is generated internally by the tool itself, even when no icon is specified.

This confirms that the notion-mcp-server has a defect where it automatically attaches a default, malformed icon object to the pages.create API payload, making it impossible to add entries to any database.